Google Git
Sign in
pigweed / pigweed / quickstart / bazel / cde92ed44b5dcf0c9b8692113d80795cff3f1f43
commitcde92ed44b5dcf0c9b8692113d80795cff3f1f43[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jul 23 20:42:39 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 23 20:42:39 2024 +0000
tree9143b66458660bbb77320de560e6ea921225e8ed
parent5e6ddf5e5ee3a2ad9aff8d5d460afb3e799c0863 [diff]
roll: pigweed, pw_toolchain 2 commits

9f0c23cb1eca790 pw_ide: Associate target groups with active files
18bd36eb28c85c1 targets/rp2040: Enhance on-device testing instruct

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