Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 9dd245485245f99d9cba4ff7c2aaa6ad529a5b30
commit9dd245485245f99d9cba4ff7c2aaa6ad529a5b30[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue May 14 04:11:50 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue May 14 04:11:50 2024 +0000
treedca92ef4fc9f6c184919f21a68e71d3be921343b
parent88540dc5f7e5a9271822352fab7ce029ae940e2d [diff]
[third_party/pigweed] Roll 2 commits

170ad30163fb5ab pw_transfer: Add py_proto_library target for updat
f55e8b048419481 targets/rp2040: pre_init and freertos config

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 430a4df2aea9b2e..170ad30163fb5ab
Roller-URL: https://ci.chromium.org/b/8747994003490669601
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I9eeac8120542c34d6a4de799278d5988a0b3346e
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209758
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: dca92ef4fc9f6c184919f21a68e71d3be921343b
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  13. README.md
  14. requirements.in
  15. requirements_lock.txt
  16. WORKSPACE
README.md

Pigweed: minimal Bazel example

This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.

Cloning

git clone --recursive https://pigweed.googlesource.com/pigweed/quickstart/bazel

If you already cloned but forgot to include --recursive, run git submodule update --init to pull all submodules.

TODO: b/300695111 - Don't require submodules for this example.

Building

We‘ll assume you already have Bazel on your system. If you don’t, the recommended way to get it is through Bazelisk.

To build the entire project (including building the application for both the host and the STM32 Discovery Board), run

bazel build //...

To run the application locally on your machine, run,

bazel run //src:echo

Flashing

To flash the firmware to a STM32F429 Discovery Board connected to your machine, run,

bazel run //tools:flash

Note that you don't need to build the firmware first: Bazel knows that the firmware images are needed to flash the board, and will build them for you. And if you edit the source of the firmware or any of its dependencies, it will get rebuilt when you flash.

Communicating

Run,

bazel run //tools:miniterm -- /dev/ttyACM0 --filter=debug

to communicate with the board. When you transmit a character, you should get the same character back!