Google Git
Sign in
pigweed / pigweed / quickstart / bazel / bed86bc17728cfa2ae9892b9ba66f830414d9676
commitbed86bc17728cfa2ae9892b9ba66f830414d9676[log] [tgz]
authorArmando Montanez <amontanez@pigweed.infra.roller.google.com>Sat Jun 15 00:22:44 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Jun 15 00:22:44 2024 +0000
tree823415fbaf9cc6a6990fd8c9cdc589ebb5c479c2
parentecc9e616f405f2df88e90ca6a248fae849f8fc78 [diff]
roll: pw_toolchain, pw_toolchain: targets/rp2040: Switch to use upstream develop branch of Pico SDK

Switches to use the upstream `develop` branch of the Raspberry Pi Pico
SDK.

Tested: //pw_status:status_test passes on device.
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/216234
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pw_toolchain, pw_toolchain Rolled-Commits: 1d00930758164bb..7e33056fe5871aa
Roller-URL: https://ci.chromium.org/b/8745109343828874705
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I080d9084b7db91d2b6e94d21964f3e490caaa7b7
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/216103
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 823415fbaf9cc6a6990fd8c9cdc589ebb5c479c2
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. BUILD.bazel
  9. echo.bzl
  10. LICENSE
  11. pigweed.json
  12. README.md
  13. requirements.in
  14. requirements_lock.txt
  15. WORKSPACE
README.md

Pigweed: minimal Bazel example

This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.

Cloning

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.

Building

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

Flashing

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.

Communicating

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!