| commit | ac13aaf3f0f22f982e737ad8d0e228a0161cc630 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri Jun 28 08:33:30 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 28 08:33:30 2024 +0000 |
| tree | 8c36374e418f14def62297cb5be4a13adc764050 | |
| parent | 094d6090b42c8882c1ca94b7e729b7f2c766a2e6 [diff] |
roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Add infrastructure for SCA operations Add HCI definitions and test operations related to retrieving sleep clock accuracy (SCA). Original-Bug: b/311639272 Test: fx test //src/connectivity/bluetooth/core/bt-host Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/954354 GitOrigin-RevId: cab5c1d7946a9a781518316a1663866570ed3dff Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/214676 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 14b2e4c65d8b10d..0d8e8401d47fe12 Roller-URL: https://ci.chromium.org/b/8743900762815830785 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Id10d04aa47fd5ac76818abe7ad1b1c419b8cca6d Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218796 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>
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!