commit | 8684d64b9a8cee063b1c9754b3fcea33f2a715a5 | [log] [tgz] |
---|---|---|
author | Jason Graffius <jgraff@pigweed.infra.roller.google.com> | Tue Aug 06 20:51:00 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 06 20:51:00 2024 +0000 |
tree | 4abb7f95a51dec3ebf1a7c326093f33b128e8554 | |
parent | 1f7860428d6615c61ad4dc6e41c2c6dac6d0a36f [diff] |
roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Use emboss for LELongTermKeyRequestReply Use an emboss view for generating an LELongTermKeyRequestReply instead of a CommandPacket. Original-Bug: b/42167863 Test: fx test //src/connectivity/bluetooth/core/bt-host Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1084052 GitOrigin-RevId: 44b1434d3ef70bb7c61e6c39d986e60b9f03c46c Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/227011 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: d75af95f4e045d8..8aa67d2d1c0c82b Roller-URL: https://ci.chromium.org/b/8740321005209557185 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I81a1aafbf3a6cf86ea27c36b0b5255617fdd45c6 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/227891 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: 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!