roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Reland "Integrate LegacyPairingState with ..."

Reland "Integrate LegacyPairingState with ..." PairingStateManager"

This is a reland of commit 31a9d97a99e1571ad674961a0647b3de85d9265e

Relanding this with no changes. Originally reverted because there was no
configuration to disable/enable legacy pairing (added in fxr/1102453).

Original change's description:
> [bt][gap] Integrate LegacyPairingState with PairingStateManager
>
> This CL wires up the legacy pairing process code to the rest of the
> system via the PairingStateManager.
>
> Depending on the pairing events we encounter before/after the ACL
> connection is complete, or depending on the result of interrogation with
> the peer, we will tell the PSM whether to use SSP or legacy pairing.
>
> Bug: b/42173830
> Test: fx test //src/connectivity/bluetooth
> Manual Test:
> - Paired and streamed audio to/from Nelson DUT with iOS and veho devices
>   supporting SSP to ensure SSP still functions
> - Paired and streamed audio to/from Nelson DUT with iOS and veho
>   devices. Cherry-picked fxr/1078858 to simulate legacy pairing
>
> Change-Id: Ibf745d6452b5f8fc53dbd16101f2cc3d6a20c114
> Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1062293
> Reviewed-by: Ben Lawson <benlawson@google.com>
> Reviewed-by: Marie Janssen <jamuraa@google.com>
> Commit-Queue: Lulu Wang <luluwang@google.com>

Original-Bug: b/42173830
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1102393
GitOrigin-RevId: 52ee3d21a3b09f3139ec8b30681ca92e760350d4
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/232771

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 7dabba55efacd17..fe1758863affc08
Roller-URL: https://ci.chromium.org/b/8738227658157187121
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I842c161a6fda33219d1ce3b714ebb1967d3b1e69
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/232564
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>
1 file changed
tree: eebdb2dcd84fb9abed93d45839c5b285283ed93e
  1. .github/
  2. .vscode/
  3. apps/
  4. modules/
  5. system/
  6. targets/
  7. tools/
  8. .bazelignore
  9. .bazelrc
  10. .bazelversion
  11. .buildifier.json
  12. .clang-format
  13. .clangd.shared
  14. .gitignore
  15. .pw_console.yaml
  16. AUTHORS
  17. BUILD.bazel
  18. CONTRIBUTING.md
  19. LICENSE
  20. MODULE.bazel
  21. OWNERS
  22. pigweed.json
  23. README.md
README.md

Pigweed: minimal Bazel example

This repository contains a minimal example of a Bazel-based Pigweed project. It is a LED-blinking service (featuring RPC control!) for the Raspberry Pi Pico. It can also be run on any computer using the included simulator.

Getting the code

git clone https://pigweed.googlesource.com/pigweed/quickstart/bazel pw_bazel_quickstart
cd pw_bazel_quickstart

Dependencies

The only dependency that must be installed is Bazelisk.

Bazelisk is a launcher for the Bazel build system that allows for easy management of multiple Bazel versions.

Instructions for installing Bazelisk can be found here.

Running on the simulator

To run the simulator, type: bazelisk run //apps/blinky:simulator_blinky Then, in a new console, connect to the simulator using: bazelisk run //apps/blinky:simulator_console

Running on hardware

To start, connect a Raspberry Pi Pico, Pico 2, or debug probe via USB.

To run on the Raspberry Pi Pico, type: bazelisk run //apps/blinky:flash_rp2040 Then, in a new console, connect to the device using: bazelisk run //apps/blinky:rp2040_console

Controlling the LED

Once connected with a console, RPCs can be sent to control the LED. Try running:

device.set_led(True)
device.set_led(False)
device.toggle_led()
device.blink(blink_count=3)

Running unit tests on the host device

bazelisk test //... will run the unit tests defined in this project, such as the ones in modules/blinky/blinky_test.cc.

Running unit tests on hardware

bazelisk run @pigweed//targets/rp2040/py:unit_test_server in one console followed by bazelisk test //... --config=rp2040 will also allow running the unit tests on-device.

Next steps

Try poking around the codebase for inspiration about how Pigweed projects can be organized. Most of the relevant code in this quickstart (including RPC definitions) is inside modules/blinky, with some client-side Python code in tools/console.py.