| commit | d22a9a86b94fe9ed00370643ade66e894dc3245f | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Apr 11 00:44:29 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 11 00:44:29 2024 +0000 |
| tree | 62ef10bc84fbdd2da8e803d4a725e160be607ac1 | |
| parent | 7d28ede7f709f854b487fa8efc8cce067a1b5aab [diff] |
[third_party/pigweed] Roll 2 commits e79414ec1071a38 clang: Fix `std::array` iterators c1a9043d74cf12d pw_cli: Update ToolRunner type hints https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 262a9aaf40ddbe6..e79414ec1071a38 Roller-URL: https://ci.chromium.org/b/8750996780316929873 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ic55ba1d50f5d4d66bb3e50d75123825ab3ce0ddb Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/202992 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!