| commit | 81081000207bed1b7d9294fbc08a929d225df6b3 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Sun May 19 04:15:40 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sun May 19 04:15:40 2024 +0000 |
| tree | 50f4b3033ca2350210424e4b62e6b291f9d715ab | |
| parent | cc5d313eb58e46b086d8debebc9ac6450143020d [diff] |
[roll third_party/pigweed] roll: 310, 311 310 From: git_revision:bb28159eee347b29eaa0628a005436040beba045 To: git_revision:3a93dbec943d0aa9bb20601dbcf618c956b6dbb4 311 From: git_revision:bb28159eee347b29eaa0628a005436040beba045 To: git_revision:3a93dbec943d0aa9bb20601dbcf618c956b6dbb4 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/210433 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: eb7a4e724f6205f..19c5ce1182033b6 Roller-URL: https://ci.chromium.org/b/8747540781945296721 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I4fcfce4cb9c813374acff805703d104e8561683e Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210435 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!