| commit | 17558f3cfc5eeeb66c4456b519f918232887ec7a | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Mar 26 17:38:48 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 26 17:38:48 2024 +0000 |
| tree | 991dd32d21eca5ede00c14046e9452aee51257c3 | |
| parent | 633b29fe5e74aff2e6e40f2ad53767ff1c165a5a [diff] |
[third_party/pigweed] Roll 3 commits 55b88ef80fc2403 pw_channel: Split open bits for read and write be2ee681c2c0176 pw_async2: Add PendFuncTask a9d379800be4ccd pw_allocator: Distinguish between requested, usabl https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: c59bb69e5e17000..55b88ef80fc2403 Roller-URL: https://ci.chromium.org/b/8752382544910045745 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I31878bbcc685b70361b902f7590215a72e40ebdc Reviewed-on: https://pigweed-review.googlesource.com/c/example/echo/+/200151 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/example/echo
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!