| commit | 6dd635345330b1637f3ba42f0193e528a735a211 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Jul 17 15:50:47 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 17 15:50:47 2024 +0000 |
| tree | 1af7d3dc6fbe83a6b22d358451a41bd7fe0314f4 | |
| parent | 733ff67312360a69734f394ac9835c2128ea7518 [diff] |
roll: pigweed, pw_toolchain 8 commits a8285a5c71eebb7 pw_bluetooth_sapphire: Modernize fuchsia.hardware. aa4a8e3d13ed126 pw_bluetooth_sapphire: Rename to secure_simple_pai 0c81249d91bb21b pw_bluetooth_sapphire: Use weak hci::BrEdrConnecti 61111f8a0a8a584 pw_bluetooth_sapphire: Create and use PairingState fed1a4ac940f060 pw_bluetooth_sapphire: Implement GetCodecLocalDela 2ff9fd8832b11ad pw_bluetooth_sapphire: Add Bazel rules for FIDL la e8a0c91ac25a4a2 pw_bluetooth_sapphire: Refactor ScoConnection 2036fdef704762d pw_bluetooth_sapphire: Fix max connection event le https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: a622862b3f0bc5d..a8285a5c71eebb7 Roller-URL: https://ci.chromium.org/b/8742151832446277137 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ideb4c7b0c2192e2ec7e735abd2e0f53b01674209 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223812 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!