roll: pigweed, pw_toolchain: pw_toolchain: Register Cortex-M7 toolchain We apparently added this toolchain in http://pwrev.dev/183160, but forgot to register it! This is pretty confusing, because we register all the other Cortex-M toolchains. See https://discord.com/channels/691686718377558037/735952592894689350/1269916490614964224 for an example of someone affected by this. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/227598 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 71c4c844f102502..b780dd700cfaf17 Roller-URL: https://ci.chromium.org/b/8740420305671349169 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I512b1b21dfd4eefb31e8083e062cfdae8d00bbce Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/227691 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!