| commit | aee2c680353dbf441d113f92989584bf247d9819 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri Apr 19 21:52:09 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 19 21:52:09 2024 +0000 |
| tree | 01a0173a6979c443c3a78fe1d1e897863fc52b47 | |
| parent | a04de3991c43cc25fc29537b7c490f4ff631a0c8 [diff] |
[third_party/pigweed] Roll 3 commits 5da0b7bbfa9736d pw_presubmit: Drop '.' from Bazel symlinks f7bed9a05a09cf0 docs: Update changelog 4d042f415cfe02e pw_tokenizer: Add missing CMake dep https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 913b39f93ad35b7..5da0b7bbfa9736d Roller-URL: https://ci.chromium.org/b/8750192255296754433 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ie416273ffea863a377a9e1b886d3b95173d8666a Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/204950 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!