Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 8be72876b81b56cd44e301871e13fafa3e554902
commit8be72876b81b56cd44e301871e13fafa3e554902[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Jun 21 20:10:36 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jun 21 20:10:36 2024 +0000
tree79ddc7fb4c4a50e04be9056a28dd92d09e9bbe6e
parent98cd496402f8e730baacd5a509cb84a3545ef36f [diff]
roll: pw_toolchain, pw_toolchain 3 commits

144113cb55fa118 pw_build: Introduce boolean_constraint_value
2c02684d3e6344c pw_bluetooth: Add PinCodeRequestReplyCommand Embos
3a6c587166bb34e pw_bluetooth: Add PinType enum

https://pigweed.googlesource.com/pigweed/pigweed
pw_toolchain, pw_toolchain Rolled-Commits: 9c34c1d5ec37823..144113cb55fa118
Roller-URL: https://ci.chromium.org/b/8744492774404670737
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I51701a81ec19d62daf4fc9f4355295dbadf09e06
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/217159
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: 79ddc7fb4c4a50e04be9056a28dd92d09e9bbe6e
  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!