commit | 64fa9f89dea27efff59602adc4ccde7357d4f898 | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Mon May 06 19:05:53 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 06 19:05:53 2024 +0000 |
tree | 661cd26b33addf130cc5b5c6da92786b25431e6a | |
parent | 4be6940edaf4eed6c2027099b1022735d2f1a374 [diff] |
[third_party/pigweed] Roll 3 commits d176d28ac80b3af pw_multibuf: Remove deprecated Chunk::DiscardFront 917922749ee0a18 pw_allocator: Fix data race 6dc5adea0df071c pw_allocator: Add BucketBlockAllocator https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 825f89f0c2fd45d..d176d28ac80b3af Roller-URL: https://ci.chromium.org/b/8748662540093715825 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I8f512e95e06842273e75be8b7b2acf1ed6cc0de7 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/208552 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!