| commit | 6fe6c06cb9f9a577eb637b906535d3df7f8654f3 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Jul 17 15:38:17 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 17 15:38:17 2024 +0000 |
| tree | 2e4aa4870b64e9d796c6afce79d2ac9d90725d22 | |
| parent | 004686ce8faf526ba265654015e0d30110b42e85 [diff] |
roll: pigweed, pw_toolchain 9 commits 2265b2568b2ddc9 pw_bluetooth_sapphire: Ensure command is supported eb4af40890efea5 pw_bluetooth_sapphire: Use duration_cast for const a5ca74b914e8205 pw_bluetooth_sapphire: Implement extended adv. pdu 5cf904b2b9af5fa pw_bluetooth_sapphire: Use `ull` constants for enu 41608a281538865 pw_bluetooth_sapphire: Update semantics of `bredr. f1ee471410b4b2c pw_bluetooth_sapphire: Add the credit-based flow c 72a8ca6b98eb503 pw_bluetooth_sapphire: Migrate LEAdvertisingReport 40351f96a88b4cf pw_bluetooth_sapphire: Lenient LEGetVendorCapabili 2295d1150aa5748 pw_unit_test: Removed duplicate from forwarded var https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 5522843e83b016f..2265b2568b2ddc9 Roller-URL: https://ci.chromium.org/b/8742152635259349441 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ie603eaf97eb52e0bdc44d855ed2344392595f33e Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223791 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!