| commit | 905c9f3e91229d79b70e487608c6e8c530d292e6 | [log] [tgz] |
|---|---|---|
| author | Ali Saeed <saeedali@pigweed.infra.roller.google.com> | Mon Jul 08 23:54:12 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 08 23:54:12 2024 +0000 |
| tree | 109a317900e6d32d17c3085dd706342d19ad8703 | |
| parent | 89da039867e85209b5dbefd45e2e56a8af9eefdb [diff] |
roll: pigweed, pw_toolchain: pw_bluetooth_proxy: ProxyHost supports multiple sends Expand ProxyHost H4 packet storage to multiple buffers to support multiple in-flight ACL sends. Add default constructor to H4PacketWithH4 to allow the construction of std::arrays of those packets in tests. I've manually confirmed that tests pass with a variety of values for kNumH4Buffs, including 1, 2, 20, & 100. Original-Fixed: 348680331 Original-Bug: 326499764 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/220573 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 6f7b53311728507..a4f432177a7e2cf Roller-URL: https://ci.chromium.org/b/8742936816628869393 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I62042ededd03a97753fae110518f224749c1995e Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/220656 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!