| commit | 4bce88a8cb282e9ecb32d36ad64c6609abbabd48 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri Apr 12 18:45:21 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 12 18:45:21 2024 +0000 |
| tree | d2fca1be0c71795e5d411e9e2b19dbfc34ddad9a | |
| parent | c049fc8f66e61c37eaaf6f1da73e5501034ce6ab [diff] |
[third_party/pigweed] Roll 3 commits 9375570a863aa43 pw_allocator: Rename TrackingAllocatorImpl f1f990d9174d855 pw_transfer: Convert arguments to std::fstream con 69ee1ccf3ef5680 emboss: Loosen Emboss cmake dependency tracking https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 23691711b80943a..9375570a863aa43 Roller-URL: https://ci.chromium.org/b/8750838152274152561 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ie76b9c27daaacf52dcc5e57f3ac35f206f84502c Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/203191 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!