| commit | 1d9ef129319cea7afdba65ae4d4c75b417729df5 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri Apr 12 00:44:52 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 12 00:44:52 2024 +0000 |
| tree | 2cff210e0e05cde42ca38ca701249f3545b9266e | |
| parent | 1cb8e0d26a2e834a40973bec1bd8f4a2470d99f0 [diff] |
[third_party/pigweed] Roll 2 commits 54c7a6dbc4ad7fc pw_build: Collect wheel fix c1e0bee4e3ec707 pw_sensor: Provide a validator https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 4a9b1e019b19eb4..54c7a6dbc4ad7fc Roller-URL: https://ci.chromium.org/b/8750906135528788513 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I31a002c8c2dffb18353a8183b6e8878a291abaf6 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/203052 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!