| commit | 633b29fe5e74aff2e6e40f2ad53767ff1c165a5a | [log] [tgz] |
|---|---|---|
| author | David Rees <drees@pigweed.infra.roller.google.com> | Tue Mar 26 03:57:34 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 26 03:57:34 2024 +0000 |
| tree | 77c3f5cac95ed0135f2af82a86073dce80678090 | |
| parent | 4ef79c8e9bd2118b1f7d215ec13601f7f9e83a7c [diff] |
[roll third_party/pigweed] pigweed_bluetooth: protocol.h comments tweak Super minor tweaks to make comments consistent for opcodes. Test: Tested in presubmit step gn_chre_googletest_nanopb_sapphire_build Original-Bug: 326499650 Original-Bug: 326499611 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/199532 https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 460176817477441..c59bb69e5e17000 Roller-URL: https://ci.chromium.org/b/8752434213395522225 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I609d682dc8126ef5ceff8850b359f295e5855167 Reviewed-on: https://pigweed-review.googlesource.com/c/example/echo/+/199970 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.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/example/echo
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!