Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 6f44ac01e8e304de1887d34133e81b82908d5e82
commit6f44ac01e8e304de1887d34133e81b82908d5e82[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Jul 10 21:27:15 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 10 21:27:15 2024 +0000
tree9e78730444baee31afed9f68db4f927a660e255f
parentea25c7d7eea62698186e01df39e935f510a01b0f [diff]
roll: pigweed, pw_toolchain 3 commits

fea8942141d1d72 pw_bluetooth_sapphire: Implement ExtendedLowEnergy
6901feb705154f7 pw_bluetooth_sapphire: Enable bt-host component
4e95e9dc76dda66 pw_bluetooth_sapphire: Support ISO Channel FIDL Pr

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 1fc96205b72d872..fea8942141d1d72
Roller-URL: https://ci.chromium.org/b/8742767692193337105
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I3f98cf6c74839756aca5f1b0eda4c9e334a7857a
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/221534
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: 9e78730444baee31afed9f68db4f927a660e255f
  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!