commit | 3bab5afc6cd5cbcc30d6ae93f5d1c58d9f1cf948 | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Jul 18 03:46:04 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 18 03:46:04 2024 +0000 |
tree | adf33a79fc2dc65db847ab8c45563d48449c13e6 | |
parent | 626fa904ae7ed5c8774abe2af4f878526824e374 [diff] |
roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Remove CommandPacketVariant Completely remove the CommandPacketVariant from SequentialCommandRunner and use EmbossCommandPackets only. Original-Bug: b/42167863 Test: fx test //src/connectivity/bluetooth/core/bt-host Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1083613 GitOrigin-RevId: 162ee1d6f9b07702625c7e4bdab2625e68afbfa6 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/224041 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 2cb52a5c040a068..da931640a3ceaa3 Roller-URL: https://ci.chromium.org/b/8742107707981284337 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I8a03e80a37435c172e7f06016354ab16b0dff8f0 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223824 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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!