| commit | 710e351e648c162c8b32be059db02aee37fc381c | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Jul 18 20:52:01 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 18 20:52:01 2024 +0000 |
| tree | 9bbfcabdd981e58fa04b7dbf78e384584c1ef7ba | |
| parent | 8e132cc8dc7d64363ec29d4fc0a36f6d691f8491 [diff] |
roll: pigweed, pw_toolchain 3 commits 643065036063709 pw_sensor: Implement attributes, channels, trigger 802073fe6021b6e pw_ide: Patch Bazelisk into VSC terminal f2261b9bad2a495 pw_async2_epoll: Fix block on racing wakeups https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: a17b318ce670eae..643065036063709 Roller-URL: https://ci.chromium.org/b/8742042295383170209 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I963ee78f4b75fb016e9b846c26fe869230c488c6 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/224411 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!