Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 742a77d3498c20d518029d78e537d6ec3fbfc3eb
commit742a77d3498c20d518029d78e537d6ec3fbfc3eb[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Jun 26 20:07:26 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jun 26 20:07:26 2024 +0000
tree9fec3a0809cd0566781d3a50e4f4a81123261107
parent7e89c45785e2abe96a2f26dc9f510b688b6b94f2 [diff]
roll: pigweed, pw_toolchain 4 commits

5dd7c05d4169558 rp2040: Add IFTT to keep the rp2040 transition and
1dbd4a434d58ba8 pw_presubmit: Add check for rp2040_binary transiti
0ea6a01ffea423f rp2040: Add missing backends
73b4c41acc7e8b5 pw_system: Async packet processing component

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 64f458827b65993..5dd7c05d4169558
Roller-URL: https://ci.chromium.org/b/8744038208810747441
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: If05ffd7dd6093ac95a030a181e97f8058cb84f8f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218452
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 9fec3a0809cd0566781d3a50e4f4a81123261107
  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!