| commit | d6f253bca3abec038ac96080ae31f04f347f57cd | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Apr 23 21:55:04 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 23 21:55:04 2024 +0000 |
| tree | 3cd7999c4164bb4d1e6f530624566cde093af914 | |
| parent | 322308d9032ae6a6ade31787295814a99f4d8fd8 [diff] |
[third_party/pigweed] Roll 5 commits 4c0dd405e0eedfa pw_build_info: Make the python module importable a9707e739fefa6f pw_allocator: Fix SynchonizedAllocator data race 3d2be38e99af311 pw_presubmit: Remove --verbose_explanations flag 69675d0eddb6ce8 pw_transfer: Implement adaptive windowing in Java 0ce38d914d7f6de pw_presubmit: Use _LOG global for logging https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 1e72e7e55cef252..4c0dd405e0eedfa Roller-URL: https://ci.chromium.org/b/8749829645146017857 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I5ec7898b1c59738c15506574e39a22a12112b2b2 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/206013 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!