Google Git
Sign in
pigweed / pigweed / quickstart / gn / f8d6b530844da0b87faa1835dc42da12df30e6e8
commitf8d6b530844da0b87faa1835dc42da12df30e6e8[log] [tgz]
authorJosh Conner <joshconner@pigweed.infra.roller.google.com>Sat Mar 30 15:34:42 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Mar 30 15:34:42 2024 +0000
treef71ca6b80e81f472aef5af7c79bc47eeaaedf8bc
parent3758d1d406fd39989ba33c2c390e30cdd68f9695 [diff]
[roll third_party/pigweed] pw_bluetooth: Add more opcodes

Add definitions for missing opcodes, many related to LE audio
features such as ISO channels, CIG/CIS/BIG, SCA, and periodic
advertising.

Test: Builds
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/201130

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 314a6228d8b6aa8..a63e2f7eb487832
Roller-URL: https://ci.chromium.org/b/8752027894741640321
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I755363dd432ba901e53d80650a4f04020d3a2c01
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/200942
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: f71ca6b80e81f472aef5af7c79bc47eeaaedf8bc
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. README.md
  12. requirements.in
  13. requirements_lock.txt
  14. 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!