Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 9f46182a5511507ed69d7b1ece646193386ac9a7
commit9f46182a5511507ed69d7b1ece646193386ac9a7[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Aug 06 23:52:34 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Aug 06 23:52:34 2024 +0000
treec0416bb33c91fa771687a1653acd3a8c4bd63589
parentb17a2c583bffa4d9a086c63af75441ae81cd05a1 [diff]
roll: pigweed, pw_toolchain 2 commits

45d1e293f8db895 pw_bluetooth_sapphire: Add SetupDataPath FIDL hand
aa2426da2f136c1 pw_bluetooth_sapphire: Create abstract base for Is

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: bdf853eca30b118..45d1e293f8db895
Roller-URL: https://ci.chromium.org/b/8740309574669462449
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Iac761da38895c8d5636147f7fb258d16bd328dda
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/227892
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: c0416bb33c91fa771687a1653acd3a8c4bd63589
  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!