| commit | fb23edaee250f25d5dd179803e88274913a8dc54 | [log] [tgz] |
|---|---|---|
| author | Jonathon Reinhart <jrreinhart@pigweed.infra.roller.google.com> | Fri Jun 21 16:51:01 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 21 16:51:01 2024 +0000 |
| tree | 6fd8b16f1683b79b7435cb847c30ac326915ec5a | |
| parent | c1d4d84254c30ab6af74dc262906c8e8eab22f00 [diff] |
roll: pw_toolchain, pw_toolchain: pw_spi_mcuxpresso: Separate Bazel build targets These now match the GN build targets, except there is no all-encompasing pw_spi_mcuxpresso target. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/217313 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pw_toolchain, pw_toolchain Rolled-Commits: d3e6e664ebf362e..9c34c1d5ec37823 Roller-URL: https://ci.chromium.org/b/8744503695740191089 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ia2ec837113ca39d6c774055bd8a352eb59a08078 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/217158 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!