| commit | e737dc1cbd43f711a0e5a01912910d3336c5d8f2 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Apr 04 18:42:46 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 04 18:42:46 2024 +0000 |
| tree | e59e843a6efceda9d0f56a38189d6464d519c8ed | |
| parent | 6c045eba674c3acd8c6ad96f67f872914528bef1 [diff] |
[third_party/pigweed] Roll 2 commits c68babc5337f950 pw_async2: Add Poll::Readiness helper ef7a6d3ac854bea pw_toolchain: Fix Rust GN host build https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 83816fda4ae0793..c68babc5337f950 Roller-URL: https://ci.chromium.org/b/8751563321001436081 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: If233626abfb4101d13e0a00e084556a930cb0948 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/201931 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.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!