| commit | a04de3991c43cc25fc29537b7c490f4ff631a0c8 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri Apr 19 18:52:01 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 19 18:52:01 2024 +0000 |
| tree | efd8829ead61e202b22a77da3af24b77bbd30da5 | |
| parent | 2421ab65c22cb60ceebf059758d32a9af201aad9 [diff] |
[third_party/pigweed] Roll 3 commits 913b39f93ad35b7 pw_string: Add missing array include 26b0e265ab5836b pw_protobuf: Fix support for import_prefix on prot 393434d3ac16cc8 pw_bluetooth_*: Formatting fixes https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: b6d694586dbc0cd..913b39f93ad35b7 Roller-URL: https://ci.chromium.org/b/8750203586475516433 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Icf124204ee5c6337052ed58e417da700d3d32797 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/204890 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!