Google Git
Sign in
pigweed / pigweed / quickstart / bazel / d6afa4611024792ff95bf4e039400ab4e2c6830c
commitd6afa4611024792ff95bf4e039400ab4e2c6830c[log] [tgz]
authorTed Pudlik <tpudlik@pigweed.infra.roller.google.com>Tue Jul 23 23:43:41 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 23 23:43:41 2024 +0000
treed82efdfb13bc9c658174b2661eb3460d42f09d66
parentc2483b7dc5deb62f1c28b4cecfd7fe4701bf2be5 [diff]
roll: pigweed, pw_toolchain: targets/rp2040: Import statement fix

Fixes an import statement that was incorrectly modified in
http://pwrev.dev/211362.

Original-Bug: b/258836641
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/225754
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 4b5da9dcb374194..c67d79552acb924
Roller-URL: https://ci.chromium.org/b/8741578486111542545
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ic10612c2ca3c5379c4d54d73515eab008d003d32
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/225637
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>
1 file changed
tree: d82efdfb13bc9c658174b2661eb3460d42f09d66
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  13. README.md
  14. requirements.in
  15. requirements_lock.txt
  16. 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!