roll: pigweed pw_bluetooth: Add Emboss definitions for AVCTP/AVRCP interception

Add Emboss protocol enums and structure fields to support AVCTP/AVRCP
offload interception and filtering in Pigweed:
- Define AvcOpcode enum (VENDOR_DEPENDENT, UNIT_INFO, SUBUNIT_INFO,
  PASS_THROUGH) derived from AV/C Digital Interface Command Set General
  Specification v4.2 Section 5.5.
- Define AvrcpEventId enum (PLAYBACK_STATUS_CHANGED, TRACK_CHANGED,
  PLAYBACK_POS_CHANGED, NOW_PLAYING_CONTENT_CHANGED, VOLUME_CHANGED,
  etc.) derived from Bluetooth AVRCP v1.6.2 Section 6.7 / Appendix E.
- Define AvrcpPduId enum (GET_CAPABILITIES,
  LIST_PLAYER_APPLICATION_SETTING, GET_ELEMENT_ATTRIBUTES,
  GET_PLAY_STATUS, REGISTER_NOTIFICATION, SET_ABSOLUTE_VOLUME) derived
  from Bluetooth AVRCP v1.6.2 Section 6.
- Define AvrcpVendorDependentPacket struct
- Keep struct fields as UInt for immediate non-breaking compatibility.

Note: Subsequent changes in this commit stack will adopt these enum
definitions in downstream repos and upgrade struct fields to strongly
typed enums.

Test: emboss tests
TAG: agy
CONV: 58d89db3-0dcf-4de1-bb5b-67b2ccdc325b
Original-Bug: 538182735
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/441632
Original-Revision: b825f50df84e64ed21d1334cd86e011ae8c3f18b

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: b87071e328a1f0..b825f50df84e64
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8675316823467554001
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I0d416a037fe91a7e525ac5022621aa9f1c6ae2a1
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/442793
1 file changed
tree: fa9a837d5b388749e7be14aa199f651b24a3cc7c
  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. .clang-tidy
  14. .clangd.shared
  15. .gitignore
  16. .pw_console.yaml
  17. .pylintrc
  18. AUTHORS
  19. BUILD.bazel
  20. CONTRIBUTING.md
  21. LICENSE
  22. MODULE.bazel
  23. MODULE.bazel.lock
  24. mypy.ini
  25. OWNERS
  26. pw
  27. README.md
  28. workflows.json
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.