roll: pigweed, pw_toolchain 9 commits a622862b3f0bc5d pw_bluetooth_sapphire: Add AdvertisingData.ToStrin 8b518ec2b747f12 pw_bluetooth_sapphire: Make UUID string parsing op ec2a45e92ab2918 pw_bluetooth_sapphire: Add Adapter::GetSupportedDe 9695b4b71c9a788 pw_bluetooth_sapphire: Clean up legacy advertising 135b5344b4b2750 pw_bluetooth_sapphire: Add missing climits include 4b00cebc95b7131 pw_bluetooth_sapphire: Add Emboss support to SendC 3688ecf89dbc109 pw_bluetooth_sapphire: Improve naming of android n 993d153724f7fc9 pw_bluetooth_sapphire: Migrate emboss aliases to n 196ab220be84690 pw_bluetooth_sapphire: Add tests for LE Read Max. https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 2265b2568b2ddc9..a622862b3f0bc5d Roller-URL: https://ci.chromium.org/b/8742152236142117985 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I29ccf74c451c223276451c7de43ceafea35054e9 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223811 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!