commit | 8c5dc2e8480a9420c876a80db6ec105d8eb5054e | [log] [tgz] |
---|---|---|
author | Josh Conner <joshconner@pigweed.infra.roller.google.com> | Thu May 09 13:08:28 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 09 13:08:28 2024 +0000 |
tree | eb82323d089bcc702a269c8aa4f879f7134e5550 | |
parent | d285a7399aa5e662aab81b67682123700f243589 [diff] |
[roll third_party/pigweed] pw_bluetooth: Add a constant for max controller delay Add a virtual field for the maximum local controller delay in the ReadLocalSupportedControllerDelayCommandCompleteEvent. Test: pw presubmit --step gn_chre_googletest_nanopb_sapphire_build Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/209271 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: cbb3917c36a4f77..56b3cbf0ec8010a Roller-URL: https://ci.chromium.org/b/8748413239436695025 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ib77ce6a506f91a90979cefb4c132f0495bbbde05 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209078 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: 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!