Google Git
Sign in
pigweed / pigweed / quickstart / bazel / ba607d1ac4ae2b067f8a9c65670223b7d06083b5
commitba607d1ac4ae2b067f8a9c65670223b7d06083b5[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jul 02 17:41:58 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 02 17:41:58 2024 +0000
treea12b397a4442bda93492dfe312980bdb7520d5d9
parentda37529d28f35a6f86e8f39d8ffa50b2a9054828 [diff]
roll: pigweed, pw_toolchain 3 commits

c703cce68d0d061 pw_bluetooth_sapphire: Refactor TxEngine to allow
877418cbee51ee1 pw_bluetooth_sapphire: Add incoming CIS request ha
ed07e6a0fe91aca pw_bluetooth_sapphire: Add IsoStreamManager class

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 0542d0d5b6b4b36..c703cce68d0d061
Roller-URL: https://ci.chromium.org/b/8743504187263733873
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ibc6133833873c65e1a2d99ee46f9c523ce2f15c9
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/219671
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: a12b397a4442bda93492dfe312980bdb7520d5d9
  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!