| commit | 26aa85d7be4c54d3a82977693ddccf9f08651ec3 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Apr 16 00:48:20 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 16 00:48:20 2024 +0000 |
| tree | 1d21cc66c031b12fbbae24e5691c5efdf9917525 | |
| parent | f163f05cf0151bc30f96d88eabd79c384a098d09 [diff] |
[third_party/pigweed] Roll 3 commits 6913460a9bd1bd6 pw_ide: Enable cmake.format.allowOptionalArgumentI 1154ff5dda14d5d pw_build_android: Update cc_defaults guidance b5b08af769c2a3a pw_rpc_transport: Soong lib names now follow style https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: b657245b27e28db..6913460a9bd1bd6 Roller-URL: https://ci.chromium.org/b/8750543545774916961 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I6b33c0957f94d600cad7a42733f61ce0318dac09 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/203713 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!