| commit | c40cfeb6da41766309143b6b47f2251bd3a72446 | [log] [tgz] |
|---|---|---|
| author | Taylor Cramer <cramertj@pigweed.infra.roller.google.com> | Thu Jun 20 22:54:36 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 20 22:54:36 2024 +0000 |
| tree | 342789aa0eb0f8f94b8e9603181522a26ae85e27 | |
| parent | eceaf222f24b7ab02e072aa8447d833e8300f089 [diff] |
roll: pw_toolchain, pw_toolchain: rp2040: Add a bazel rule for flashing Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/216314 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pw_toolchain, pw_toolchain Rolled-Commits: 23df123c1a72c91..d9bba5855b72a9f Roller-URL: https://ci.chromium.org/b/8744571297921484801 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Icfae327517305ac5a195ffc4c2527dcdab519f1f Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/217292 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!