| commit | 425c84f0e004d9529bcf600691feded073ecde7f | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Sat Mar 30 00:34:18 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Mar 30 00:34:18 2024 +0000 |
| tree | ee5245cffe5e2ef57d1ab2087c7bf8abc8c7ce25 | |
| parent | 1f1d5cf83b2934f06fc00989bbc1fb1cdba213ca [diff] |
[third_party/pigweed] Roll 5 commits 16c27d8785cb548 pw_bluetooth_proxy: Move to cpp23::to_underlying 7c532c9bbd08f7d pw_presubmit: Include doxygen html in docs_build 0052b9e092a8ca7 pw_web: NPM version bump to 0.0.17 35632f3b4d7c6f0 pw_build: Add alwayslink option to pw_cc_blob_libr ce97896f2d3cabe pw_python: Update setup.sh requirements https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: a2f414de101195b..16c27d8785cb548 Roller-URL: https://ci.chromium.org/b/8752084547508634849 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I0d1fdf5f2978ce85f5739883846cf6d019450847 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/200938 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!