roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Switch over to pw::utf8

Switches over to using `pw::utf8` instead of `ICU` for basic unicode
conversions and validation. This allows us to completely remove our
dependency on `ICU` in the bluetooth codebase which make integration for
downstrem users easier.

Original-Fixed: b/337305285
Test: fx test //src/connectivity/bluetooth/core/bt-host
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1090253
GitOrigin-RevId: ad96791bef3b429e2913fd62a00766553df09ae0
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/227020
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 0fe4fa324363134..b83d27482bb6ccf
Roller-URL: https://ci.chromium.org/b/8740242630563775009
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I12f8f4d2e3e658619488fae39ee96b8a94d33390
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/228072
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: ed061cfa173222d088f38a692763a07d40505b7c
  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!