| commit | 4e37f4fb5cfb2092b528ae23d8e262dadac50649 | [log] [tgz] |
|---|---|---|
| author | Colin Didier <cdidier@pigweed.infra.roller.google.com> | Fri Jul 26 21:46:58 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 26 21:46:58 2024 +0000 |
| tree | 9e55689fda10713ee0f990eee35e523077ffccc7 | |
| parent | d2abe3a8e1ab1fa2e0d8e0067f186e6c28014771 [diff] |
roll: pigweed, pw_toolchain: pw_chrono_stl: Move system clock and timer into separate directories Separate the public_overrides directory for the stl system clock and system timer backends so one of these backends can be picked up without bringing the headers of the other backend. If both system clock and system timer share the same public_overrides directory, then you can't use a custom system timer with the stl system clock because the headers of the stl system timer might be picked up by the compiler before the headers of the custom system timer. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/225992 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 84803f3af2d56dc..c605a3b205089cd Roller-URL: https://ci.chromium.org/b/8741314076791362865 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ibbf7abd558eda184eb65214ef9aac4561db92eae Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226253 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> 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!