roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Fix conversions from iterators to raw pointers

https://github.com/llvm/llvm-project/pull/74482 in upstream libc++
changed the return type of various iterator functions (*.begin(),
*.end(), etc) from raw pointers to iterator objects. The return types
for these functions aren't guaranteed to be raw pointers, but we have a
bunch of c++ code that assumes they are. We can get pointers from these
iterators by simply dereferencing them and taking their address
(`&*iter`).

Original-Bug: 328282937
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1010227
Owners-Override: James Robinson <jamesr@google.com>
GitOrigin-RevId: 89c40478c5fd4dfd5e64196c364da1b026fb3fde
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/221014
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 2a5f339c40c1236..97bdfeb645a92f7
Roller-URL: https://ci.chromium.org/b/8742552018064493681
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I05e1edd181db20ddb6109eb12b466672ecda551b
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/222862
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: 03e00ff7bdfc90bbdbecb891ada3731c47dac75f
  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!