roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Refactor LowEnergyScanResult to its own class

The LowEnergyScanResult class was previously a struct with all public
members used to track the elements related to a scan result. A bit
awkwardly, the advertising data and scan response data related to the
scan result was stored in LowEnergyScanner::PendingScanResult.

This change updates LowEnergyScanResult to store the advertising data
and scan response data within itself. To present a better API to users,
and to prevent accidental modification, LowEnergyScanResult is now a
class with getters and setters instead of a struct with all public
members.

Since LowEnergyScanResult stores the advertising data and scan response
data itself, we can also modify the
LowEnergyScanner::Delegate::OnPeerFound API to simply take the
LowEnergyScanResult alone instead of also taking in the data as a
separate argument. We only did that because the data was stored
separately.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/987909
GitOrigin-RevId: 9b3b47f13c3c8b41c4a00fe4a2d2a2688b9a807c
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/218975
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 5c3289c29896ea2..f219e65ac4075ab
Roller-URL: https://ci.chromium.org/b/8743458863914510497
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I897746352b081e238dce4da5b66828c7c86fd8c8
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/220031
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: 925d0242b578fcf7c332a8aa514a95c592fcefc5
  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!