Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 69b8d0d663d4d0a7812f0380361566d5658538ba
commit69b8d0d663d4d0a7812f0380361566d5658538ba[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jul 02 23:42:52 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 02 23:42:52 2024 +0000
treeeb518e638883ca5277aeea833c77e16b1da822d3
parenta30bd2f488f915701a81e8c222d9a2fa6c97c579 [diff]
roll: pigweed, pw_toolchain 3 commits

4066416d3c4eb7d pw_assert: Split up Bazel assert backend, part 1
c927404b863ed9f pw_web: Debounce grid template calc on resize
97438c6e8344be2 pw_digital_io_rp2040: Add pull up/down resistors t

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: bfaf596d3e1231c..4066416d3c4eb7d
Roller-URL: https://ci.chromium.org/b/8743481521423974849
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I3aa31275ed7b7acfc96f827d3985d4a9c4d004e0
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/219931
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: eb518e638883ca5277aeea833c77e16b1da822d3
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  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!