| commit | cfd6aa6f66bdeee6f223470142a1e7b12e7172e7 | [log] [tgz] |
|---|---|---|
| author | Wyatt Hepler <hepler@pigweed.infra.roller.google.com> | Mon Jun 24 23:23:58 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 24 23:23:58 2024 +0000 |
| tree | 451691321cf7465750b5a9a5d132e441f9612655 | |
| parent | a6d4f0cdd537134d245d5166b18bbac862c86102 [diff] |
roll: pigweed, pw_toolchain: pw_toolchain: Color diagnostics in Bazel - Enable color compiler diagnostics in Bazel. - Update comment referring to duplicate bug. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/217715 https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 3bf60a7ec0808b4..519f0b724d9394c Roller-URL: https://ci.chromium.org/b/8744207042154648721 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ie6ce938366dfb6000331df8f794d11b808ae85d9 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/217795 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: 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!