Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 0f5e9826d1332aa8dd7ff2910d239dd3e6b26aa0
commit0f5e9826d1332aa8dd7ff2910d239dd3e6b26aa0[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu May 02 22:05:38 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu May 02 22:05:38 2024 +0000
treed1dc2d969c319b47743579b8ef54b5d4e0c42ce1
parent8b732c4806c1ee9c5280402f18aa19ac21e4a627 [diff]
[third_party/pigweed] Roll 4 commits

9818527a8610c7a pw_bluetooth_sapphire: Use hci_android.emb.h
1a7803b5be6ed6f third_party: Add missing libfit deps for Android
0b7dd705b9c1159 pw_bluetooth: Rename hci_vendor to hci_android (wi
ae704b9dd8618ac pw_bluetooth: Add Vendor BQR subevent prefix

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 7b7d2fd94a5d29c..9818527a8610c7a
Roller-URL: https://ci.chromium.org/b/8749013794451977153
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Idda16f954ab0752c788437bcf7ae088566df8ba7
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/208018
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: d1dc2d969c319b47743579b8ef54b5d4e0c42ce1
  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. 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!