| commit | 94ffb84fc8ce3c6463965725e96bd679920ffa9b | [log] [tgz] |
|---|---|---|
| author | Taylor Cramer <cramertj@pigweed.infra.roller.google.com> | Fri Jul 26 18:50:46 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 26 18:50:46 2024 +0000 |
| tree | abfe4b4f653145dac2cd0b670c18358037c0b717 | |
| parent | f4c9390abb5f8c05b75562aef02827c4675f3c45 [diff] |
roll: pigweed, pw_toolchain 2 commits f73ddb4d76eb9df pw_async2: Mark Task::IsRegistered as const c52c57761a9ba39 pw_async2: Allow coroutine methods https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: f29a915bb5ea870..f73ddb4d76eb9df Roller-URL: https://ci.chromium.org/b/8741325112279622801 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I6e8b6ff9bde53f4016056583db6bbb34398ad3f5 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226025 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!