Google Git
Sign in
pigweed / pigweed / quickstart / bazel / ce72a15a4d9604b7e2d50fafbd7f6c3418477013
commitce72a15a4d9604b7e2d50fafbd7f6c3418477013[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Apr 24 00:54:59 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Apr 24 00:54:59 2024 +0000
tree9c2b4a389dbd5a453df8066715eab34ce6f6a86a
parentd6f253bca3abec038ac96080ae31f04f347f57cd [diff]
[third_party/pigweed] Roll 3 commits

a5052ba92950982 pw_allocator: Make AllMetrics internal
14e0d76298d7690 pw_unit_test: Standardize ASSERT_OK_AND_ASSIGN
dea2ecf94d39c9c pw_unit_test: Clarify status macros are gunit-only

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 4c0dd405e0eedfa..a5052ba92950982
Roller-URL: https://ci.chromium.org/b/8749818315467577217
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ieedf34e66d3d80a2b92830e2d60f29ef51c5daad
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/206014
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 9c2b4a389dbd5a453df8066715eab34ce6f6a86a
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. README.md
  13. requirements.in
  14. requirements_lock.txt
  15. 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!