| commit | 9fe0b4aa4012160e61c38b2fb57786a9905da458 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Apr 03 00:37:30 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 03 00:37:30 2024 +0000 |
| tree | b10ee1e3a67aa9490ee2139fdd0f5d98d522d39f | |
| parent | 0d8b613cd14497db0cbcae5f470fb9b6941d6ad2 [diff] |
[third_party/pigweed] Roll 3 commits
d909f52cfaf5652 pw_allocator: Restore DoDeallocate with Layout
e701eb8e91eeb0e pw_{build,module}: Allow nesting Pigweed modules i
09d24b46231e82f pw_ide: Support comp DB search path globs
https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 0540acc0b8bf0b1..d909f52cfaf5652
Roller-URL: https://ci.chromium.org/b/8751721962079103937
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I3977fe1ba0725f70a7d3c81d8a814aacadf82132
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/201554
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!