roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Add ISO support to controllers

Implement support in Banjo and FIDL controllers for ISO data
streams.

Original-Bug: b/311639690
Test: fx test //src/connectivity/bluetooth/core/bt-host
      Manual testing on Sherlock:
      - OOBE
      - A2DP (Source and Sink)
      - HFP (AG)
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/998736
GitOrigin-RevId: e8c75890a68e5a817272737408ca399edf598674
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/218992
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 73623f58298ca29..afe76e45d26332d
Roller-URL: https://ci.chromium.org/b/8742824342279543649
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I46986d15b2b2a767e1c59a6dbca57b3bbfe374f6
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/221271
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 3971ccad0aa996421ea20b18e70ead87a7f0d230
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  13. README.md
  14. requirements.in
  15. requirements_lock.txt
  16. WORKSPACE
README.md

Pigweed: minimal Bazel example

This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.

Cloning

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.

Building

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

Flashing

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.

Communicating

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!