roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Reduce scope of security_manager This adds some forward declarations and removes unnecessary includes from a few `sm` and `gap` headers to limit the amount of inter-component dependencies on the `sm` component. Original-Bug: b/337315598 Test: fx build --default \ //src/connectivity/bluetooth/core/bt-host/testing Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1084665 GitOrigin-RevId: 41625b11ecfee1b2ec8bb86f0ac72b8d42ad43d3 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/225036 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: f3360d644897271..3b0403f48dca656 Roller-URL: https://ci.chromium.org/b/8741931143891013665 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I2690f8c882ce7e8688a5275292fcd1dd72b69512 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/225136 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: 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!