Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 6f1bdfb9891bc2cb8a8badcb5435444ed0df58d2
commit6f1bdfb9891bc2cb8a8badcb5435444ed0df58d2[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Apr 09 21:43:17 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 09 21:43:17 2024 +0000
tree85586e32b0fa89cb94dc85034f09ab1491b44419
parent59f93eb8df87f5a924d9dce716240670a60401d7 [diff]
[third_party/pigweed] Roll 2 commits

d578e9425943c63 pw_bluetooth_sapphire: Change CIPD upload path
f27ca9fe526eaec pw_web: Enable column order on init

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: fb7782c0299f501..d578e9425943c63
Roller-URL: https://ci.chromium.org/b/8751098753817184913
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Id3077014c2e0554499e3b815dcb0c1774822e669
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/202811
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: 85586e32b0fa89cb94dc85034f09ab1491b44419
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. README.md
  12. requirements.in
  13. requirements_lock.txt
  14. 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!