| commit | f76650dc3fcfb725c41525a767fb19c548eadb2b | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Mon Apr 01 21:36:52 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 01 21:36:52 2024 +0000 |
| tree | 7483368dad9d9e9bc29e6299b02e19cc18bdabda | |
| parent | 55ad0ad761c479f26445c524002be26e2330e430 [diff] |
[third_party/pigweed] Roll 2 commits
18442a7e69a5b1c pw_multibuf: Replace Mutex with ISL
3c2ef28caa5205f pw_{cli,ide}: Move status_reporter to pw_cli
https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: f50d5dcf8166a74..18442a7e69a5b1c
Roller-URL: https://ci.chromium.org/b/8751823944822668577
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I455e34616bf596561e25c568517fe187f8a00b64
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/201257
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!