Google Git
Sign in
pigweed / pigweed / quickstart / bazel / c899c94d61cb99b4cf3905b3ca1e4b06ce9d137b
commitc899c94d61cb99b4cf3905b3ca1e4b06ce9d137b[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon May 20 19:17:08 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon May 20 19:17:08 2024 +0000
tree04643723aaf3d8828c1f291a983bad6afed2ac4b
parent4286d85dd0ce5f3e194026da94c8e6af8f804f5e [diff]
[third_party/pigweed] Roll 3 commits

de0813bee2778fe pw_allocator: Move large values to test fixtures
22a0e55b88e62a5 *: Update Android.bp after GetAlignedSubspan move
6e1b3f4d2039aa1 pw_chre: Update CHRE revision

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: a13c1efc6afb86f..de0813bee2778fe
Roller-URL: https://ci.chromium.org/b/8747393491716242289
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I4775a126f753974005683e43ad8b2094804e1ca9
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210522
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 04643723aaf3d8828c1f291a983bad6afed2ac4b
  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!