| commit | 149e26632a6991121f26b613f7400e0959e0fdb1 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Apr 25 00:56:03 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 25 00:56:03 2024 +0000 |
| tree | 1782a9e20f707f5361f126cab7c0ced2b7ac0cf8 | |
| parent | 0647475b5960dc06dec83ee77700d7681956081d [diff] |
[third_party/pigweed] Roll 3 commits 32ff69e60cb8ad6 pw_allocator: Clean up LibCAllocatorTest c50cd3d84714aa6 pw_allocator: Move block allocators to separate fi 4613447f11e0513 pw_presubmit: Save 'bazel info output_base' https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: f79f7c42e7921fe..32ff69e60cb8ad6 Roller-URL: https://ci.chromium.org/b/8749727665621244097 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ia2dc0390de020fe9f7afd3452f530c40dd558385 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/206216 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!