Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 1289ea830598de4e21d3910ae6d734b9c58ac8d7
commit1289ea830598de4e21d3910ae6d734b9c58ac8d7[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Jun 07 03:16:17 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jun 07 03:16:17 2024 +0000
tree889ba8cc0969266f166b651671e29e30eb138267
parent5dacba556401fd53eb79b6d6867e6244c627ff13 [diff]
[third_party/pigweed] Roll 4 commits

f20a2dc6ded67a5 pw_bluetooth: Add module metadata
13815f73d4aa893 pw_bytes: Add module metadata
d3fdc8b3a0e8d99 pw_bluetooth_hci: Add module metadata
3d3e59c25557e05 pw_build: Clarify docs on pw_elf_to_bin

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 1d82b0ff4c571fe..f20a2dc6ded67a5
Roller-URL: https://ci.chromium.org/b/8745823215337795153
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I770a1d32380e2521959174c1510bc4a09e628310
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/214520
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 889ba8cc0969266f166b651671e29e30eb138267
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  13. pigweed.json
  14. README.md
  15. requirements.in
  16. requirements_lock.txt
  17. 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!