Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 1a51d54a89ab20dab47444c0258154f75cea1b9c
commit1a51d54a89ab20dab47444c0258154f75cea1b9c[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jun 25 02:06:08 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jun 25 02:06:08 2024 +0000
tree660ad54e252cde53770f1d4271fd2cf9be7a1d43
parentbd95d1e4044725fb5ee389a5e1772bb0783b521c [diff]
roll: pigweed, pw_toolchain 3 commits

1ca76fae9309425 rp2040: Unify board selection cmdline args
e6665db1a2f466e pw_cli: Add missing modules to Bazel build
1aa0264cdafa992 roll: cipd

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 8e09a4c6339490c..1ca76fae9309425
Roller-URL: https://ci.chromium.org/b/8744196846995085009
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I483f33e7d6e1b600a58e3a80a0b53d2fbf0d2f84
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/217797
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 660ad54e252cde53770f1d4271fd2cf9be7a1d43
  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!