| commit | 8dab0eb8cb2bcb9488d052da881e2fb94af8b1a1 | [log] [tgz] |
|---|---|---|
| author | Wyatt Hepler <hepler@pigweed.infra.roller.google.com> | Tue Apr 23 19:01:27 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 23 19:01:27 2024 +0000 |
| tree | 4883df63841574b679c05d37ca5e2caf013d0197 | |
| parent | 44968877b765054803357282246ba0f2b3a67f86 [diff] |
[roll third_party/pigweed] pw_presubmit: RST format updates - Replace `.. code::` with Sphinx's `.. code-block::`. - Replace tabs with spaces. Previously, the script did this but ignored the results. - Don't replace tabs in 'none' or 'go' code blocks. - Apply RST format updates to existing files. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/204241 https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: d01aa29f9f9e113..1e72e7e55cef252 Roller-URL: https://ci.chromium.org/b/8749840591205947105 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I9984c00be1c826b8427164cd44e68b4790a854fb Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/206010 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!