| commit | e0dc8450c75d3df17cfde3f77164a95570b1945a | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Mon Apr 08 18:42:29 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 08 18:42:29 2024 +0000 |
| tree | 559320b3411a6e9b503bd8be72a8c3be31946640 | |
| parent | 7bd1d2b825efbaf9e65415b5014fb809d8d50b5e [diff] |
[third_party/pigweed] Roll 3 commits 2bd59a5ace13fb9 pw_web: Fix test format of log-source.test 28fa6003e1e2cf4 pw_build_info: Add missing header file for cmake cd34143426e9907 docs: Add Zephyr quickstart https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 0f8f2149a9608ac..2bd59a5ace13fb9 Roller-URL: https://ci.chromium.org/b/8751200724827535313 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Id505f0afa313ee542d58de5667052fff0ef5fb20 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/202530 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!