commit | 33b1ec98c7549bfadbb505f7a8e14116f2fe24db | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Jul 10 22:59:04 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 10 22:59:04 2024 +0000 |
tree | 0104a43eed772879980bf17e2a13ba423e18c39b | |
parent | 6f44ac01e8e304de1887d34133e81b82908d5e82 [diff] |
roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Unmask LE Connection Complete fxrev.dev/985356 added support for extended connections. However, somehow it got merged with only LE Enhanced Connection Complete unmasked. It didn't get merged with LE Connection Complete unmasked. We need to unmask LE Connection Complete so that the Controller knows to send us the event. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1006214 GitOrigin-RevId: e60eb09b042a745de58e9b30e419cc3075811ce8 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/221033 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: fea8942141d1d72..c89c0361d2438b6 Roller-URL: https://ci.chromium.org/b/8742764437777207809 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Id9407f82e30a4b80de86fb311bd0e713ce4a1d6b Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/221535 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!