roll: pigweed, pw_toolchain 2 commits 324ee75ec152caa third_party/emboss: Append public_deps in GN templ 446b73e84b7ae45 pw_presubmit: Remove misc program https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: a21a327d126ba0d..324ee75ec152caa Roller-URL: https://ci.chromium.org/b/8740762362331013889 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I0c66d20f99ff4a12ce68a367f3c79d5ac4765467 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/227065 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: 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!