| commit | 9f2712c5d8c3b5513a49967a16f999dc2c4390ff | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed May 08 01:07:03 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 08 01:07:03 2024 +0000 |
| tree | 0d16882917c5dd5ed215508720c5c64b1810c2aa | |
| parent | 0dd0f69e578a3f23cbe009f179c78599847b5d30 [diff] |
[third_party/pigweed] Roll 3 commits
95093534642cccc pw_bluetooth_proxy: Add cmake build rules
8cdcad7cc37aefa pw_{rpc,trace_tokenized}: Build compatibility fixe
a1802f8bb4e2c92 pw_protobuf_compiler: Disable layering_check
https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 4f0b1a7c4cd2ee2..95093534642cccc
Roller-URL: https://ci.chromium.org/b/8748549213522564113
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Id54dd8e0b2b4caa1ca8decde1403093fe78f9e40
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/208876
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!