| commit | ac835835be224ccba0615da1a323e187fe49b448 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Mar 27 03:32:18 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 27 03:32:18 2024 +0000 |
| tree | d7200d027f68e24222c4e2f1a121e81506107163 | |
| parent | b614538eca3f2af7d040907a9752e480d7cd7d43 [diff] |
[third_party/pigweed] Roll 3 commits
d595cc8bc24ce2e pw_hdlc: Add async router
9bbfe80a2ffff7c pw_{log_basic,sys_io}: Fix Soong definitions
9c33f41cda92196 pw_trace_tokenized: Fix static initialization
https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 3473c9118a43845..d595cc8bc24ce2e
Roller-URL: https://ci.chromium.org/b/8752345164693940993
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ifc1de7dc58cee670d6845cff5f3c05185f9ed57c
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/200159
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/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!