| commit | 13fbea640d6de6cdab46e784035ed711772e2a19 | [log] [tgz] |
|---|---|---|
| author | Alexei Frolov <frolv@pigweed.infra.roller.google.com> | Fri Jul 12 02:48:52 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 12 02:48:52 2024 +0000 |
| tree | 7f972931f3ee9d355a6ecc90afb2c42a49d53b8c | |
| parent | 2ddff182c36169b07a8b3000e683a0fe51d6db87 [diff] |
roll: pigweed, pw_toolchain: pw_target_runner: Increase maximum message size for binaries Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/222736 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: bf88de9f5c04467..b71abe8012cb8ce Roller-URL: https://ci.chromium.org/b/8742654001156837073 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ia1394a42ebee6cd7ec1636c2477dd325434102de Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/222660 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!