| commit | 2cd6350ef77fe0a091df69245d6fc17f483deb47 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Jul 17 15:57:11 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 17 15:57:11 2024 +0000 |
| tree | 1c6d8adc159b6555ca8338a1df5fd99e37be498c | |
| parent | 6dd635345330b1637f3ba42f0193e528a735a211 [diff] |
roll: pigweed, pw_toolchain 7 commits 41f05bde0a0e51c pw_bluetooth_sapphire: Remove alias for BrEdrConne 4be96ee0d8d1e07 pw_bluetooth_sapphire: BrEdrConnectionRequest crea 217e8726bf1c9d7 pw_bluetooth_sapphire: Add connection role to fake 57000edcfd2bb92 pw_bluetooth_sapphire: Remove double std::move in 22c3381a3cc63e3 pw_bluetooth_sapphire: Fix BrEdrDynamicChannel cra aae665e766a0865 pw_bluetooth_sapphire: Cleanup BrEdrConnectionRequ 565760fe5122a2e pw_bluetooth_sapphire: Implement IsoStreamServer https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: a8285a5c71eebb7..41f05bde0a0e51c Roller-URL: https://ci.chromium.org/b/8742151437514499041 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ie3f787a70451387a7793ddac2dde8c6a3513843e Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223793 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!