Google Git
Sign in
pigweed / pigweed / quickstart / gn / e33b1d3948656e282d75071d10255695d586d693
commite33b1d3948656e282d75071d10255695d586d693[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Apr 05 21:40:21 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Apr 05 21:40:21 2024 +0000
treeaa4367576940daf639dc38680f05a1feb6e66365
parent6c9120f535572b6efd69bf239eb67f3692efb95e [diff]
[third_party/pigweed] Roll 2 commits

1cbf2352b3e0b5e pw_bluetooth: Define LEReadMaximumAdvertisingDataL
c79856c8e746b08 pw_bluetooth_sapphire: Add arm64 release variant

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 517696e29810c51..1cbf2352b3e0b5e
Roller-URL: https://ci.chromium.org/b/8751461338962298561
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I3fc8060ad57007b1bfeb8eedde241258d265fc7f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/201988
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: aa4367576940daf639dc38680f05a1feb6e66365
  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!