Google Git
Sign in
pigweed / pigweed / quickstart / bazel / de6e6a6752150537133b00aa1b00bad20870e441
commitde6e6a6752150537133b00aa1b00bad20870e441[log] [tgz]
authorAli Saeed <saeedali@pigweed.infra.roller.google.com>Thu Jun 27 20:43:18 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jun 27 20:43:18 2024 +0000
treefdd135dc04bb3af3eacf0c4ad0f5bd395e762049
parentbad1f79d6f3f9bfeab927bb1efdc25a85535c69d [diff]
roll: pigweed, pw_toolchain 4 commits

e8d6172f4a0a8e0 pw_bluetooth_proxy: Implement basic ACL credit tra
10c7ed0e358e526 pw_bluetooth: Add NumberOfCompletedPacketsEvent
6cdc8b45342c1d5 pw_bluetooth_proxy: Implement sendGattNotify
b71d14d3879a2c3 pw_bluetooth: Add AttNotifyOverAcl to att.emb

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: befcb91b39880a5..e8d6172f4a0a8e0
Roller-URL: https://ci.chromium.org/b/8743945360725547281
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ie655953826a647773421432bf6ef976ef28d4c2e
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218771
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: fdd135dc04bb3af3eacf0c4ad0f5bd395e762049
  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!