| commit | f373830c3f03367e9e6a4df2852c8b9b2e9b3365 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed May 15 01:12:53 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 15 01:12:53 2024 +0000 |
| tree | 1d0cb30ce9ac5484d76d352622d84d9690636f6d | |
| parent | 333f8054f75ffe6c46949b070f60b70e4e12296e [diff] |
[third_party/pigweed] Roll 7 commits 5a5d85cf27c4421 [fuchsia_infra] Roll 13 commits 7ed020b6db73345 pw_bluetooth_proxy: Also support V2 of LE read buf 624978e6fb2f4fe pw_protobuf: Build common.proto with Nanopb+Soong 64b8f9177534bbf pw_sys_io_rp2040: Bazel build file update d3177c05eea8174 pw_docs: Add inline search to sidebar c1441316f6bfcc0 pw_bluetooth_proxy: Use LE read buffer event 51c17fb5e937755 pw_presubmit: Fix missing pico-sdk for docs_build https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: cd07cc170ebc110..5a5d85cf27c4421 Roller-URL: https://ci.chromium.org/b/8747914680770158929 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ide50836f14c66a280a46694623dafe64d720d95d Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209890 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!