| commit | 43d99cfbe45792aa47f14e87802e6ee72fd2e5d3 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Mar 27 21:33:01 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 27 21:33:01 2024 +0000 |
| tree | 7ab0bb86af39a7710c2699ca42b137ae4c3988f3 | |
| parent | afbf8d13b255e741eaefd4ece85f99925b2a57a9 [diff] |
[third_party/pigweed] Roll 3 commits
f52852da66260fe pw_build: Defer build directory existence check
80b4c3b3a15729d pw_{digital_io,i2c,spi}_rp2040: Update OWNERS
da90e892074c6b0 pw_{chrono,i2c,spi,sys_io}_rp2040: Update OWNERS
https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 130b688924ea31a..f52852da66260fe
Roller-URL: https://ci.chromium.org/b/8752277174368570209
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I313bf479baf9fb0cec0dd207f863d2691b4ca28d
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/200850
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.
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.
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
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.
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!