| commit | 64a7645f2bb9092683fa758eb75c732e1d1072d5 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Jul 17 16:04:18 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 17 16:04:18 2024 +0000 |
| tree | b0a56460e0a88165c5c0778f9eb4316e2e046097 | |
| parent | 2cd6350ef77fe0a091df69245d6fc17f483deb47 [diff] |
roll: pigweed, pw_toolchain 6 commits 4524992ebf7d7a4 pw_bluetooth_sapphire: Use pw_bytes for endianness d7e8d2ff283c451 pw_bluetooth_sapphire: Use pw_bytes for endianness 3e71386abd84aec pw_bluetooth_sapphire: Use pw_bytes for endianness 3ac62ffae11dbdb pw_bluetooth_sapphire: Rename link_initiated to ou a532db5b0ae5a4b pw_bluetooth_sapphire: Cleanup WriteScanEnable pac 50f4a97a1903282 pw_bluetooth_sapphire: Cleanup ReadScanEnable pack https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 41f05bde0a0e51c..4524992ebf7d7a4 Roller-URL: https://ci.chromium.org/b/8742151043827172625 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ib3552a16de79d513a209a16d720ee8914156f83c Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223813 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> 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!