| commit | 4286d85dd0ce5f3e194026da94c8e6af8f804f5e | [log] [tgz] |
|---|---|---|
| author | Armando Montanez <amontanez@pigweed.infra.roller.google.com> | Mon May 20 07:16:31 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 20 07:16:31 2024 +0000 |
| tree | 315d27a9119917febcaf5e37c6d7dd1c1053b8ca | |
| parent | a9e08ed73f801ef24c4c13723c24328b77e76ad1 [diff] |
[roll third_party/pigweed] targets/rp2040: Update openocd flashing instructions A custom build of openocd is no longer required for pico debuggers as they now operate in CMSIS DAP mode. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/210400 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 49dd44fcb1a0b68..a13c1efc6afb86f Roller-URL: https://ci.chromium.org/b/8747438810827326385 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ifdedb69211bc1179c0a5b6e609681b4bcb59bdfb Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210514 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!