Google Git
Sign in
pigweed / pigweed / quickstart / bazel / f42849830209cb2570c1a2ae411b57eea4459a22
commitf42849830209cb2570c1a2ae411b57eea4459a22[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed May 15 22:13:19 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 15 22:13:19 2024 +0000
tree6db0d593fc09e3926407190bf3f47cdc281121a3
parent72bb6db58ee27e2ff60cf615094ab065dc1a3b95 [diff]
[third_party/pigweed] Roll 4 commits

54a35ecd0d457ca pw_cpu_exception_cortex_m: Add error flag masks
42a82886e1fa154 pw_bloat: Add padding to utilization
c7128f5797ce9d4 bazel: Fix unsorted-dict-items instances
1f9748d17b29edc pw_cpu_exception_cortex_m: Fix PSP unit test

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 9d5fa2aef16857b..54a35ecd0d457ca
Roller-URL: https://ci.chromium.org/b/8747835367820323409
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I6b7da26763bc57cf43acccd81de6e38c2cb36152
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210046
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 6db0d593fc09e3926407190bf3f47cdc281121a3
  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!