| commit | 95a93a6fed461f91aba42d8501384467d06b5510 | [log] [tgz] |
|---|---|---|
| author | Taylor Cramer <cramertj@pigweed.infra.roller.google.com> | Fri Jul 19 00:14:55 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 19 00:14:55 2024 +0000 |
| tree | ce57307daf96d880990a125c6fd329998ea32ac3 | |
| parent | f881dddf5c5ca8e5ddc11103013949e4d9027822 [diff] |
roll: pigweed, pw_toolchain: pw_chrono_stl: Consolidate SystemTimer into a single thread Prevoiusly, every call to `InvokeAt` or `InvokeAfter` would create a brand new thread. This was wasteful and created unnecessary thread creation and deletion noise when debugging. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/224295 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: acbc017cab7db9b..a0bc30225ae7058 Roller-URL: https://ci.chromium.org/b/8742029506726439409 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I4c591ddbe5b41a435d424de24ce3ec1702a5144a Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/224492 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!