Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 8af4bb78cd29be4fcd24cfdf3d78a09fb698d7e6
commit8af4bb78cd29be4fcd24cfdf3d78a09fb698d7e6[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon Jun 24 20:30:46 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jun 24 20:30:46 2024 +0000
tree0cec633b57b4d277cd4a84a9b9b0119cbcde6568
parenta0b0167e31047f80231aabb505c49a8885474798 [diff]
roll: pigweed, pw_toolchain 5 commits

91a2499caca5df9 pw_bluetooth: Add PinCodeRequestEvent
24ba5be366a13fe pw_env_setup: Update cffi
2b940fce2f86437 pw_toolchain: Closer align the bazel arm-gcc flags
2e873820d53b814 pw_bluetooth: Add IoCapability enum field
3376fa7390a6906 pw_web: Add Shoelace component flag

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: ca95ef3b6b576da..91a2499caca5df9
Roller-URL: https://ci.chromium.org/b/8744218003655831985
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I94bf3a4d187beb91bc2455d9120cb13d7e96b9e2
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/217793
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: 0cec633b57b4d277cd4a84a9b9b0119cbcde6568
  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!