Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 1bdbac6effaddb80baf4d91d4dd33afed3868a16
commit1bdbac6effaddb80baf4d91d4dd33afed3868a16[log] [tgz]
authorJason Graffius <jgraff@pigweed.infra.roller.google.com>Sat Jul 13 05:44:22 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Jul 13 05:44:22 2024 +0000
tree6e8093f565c9e39a3e40c285721c4f9c1de87905
parentb1ef40916404e5029887eae2ea214734f0f4f9e2 [diff]
roll: pigweed, pw_toolchain 2 commits

2a5f339c40c1236 pw_bluetooth_sapphire: Add bt-host Bazel tests
fb0067fff348563 pw_bluetooth_sapphire: Low energy advertiser gener

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: d55ec9627e60afd..2a5f339c40c1236
Roller-URL: https://ci.chromium.org/b/8742552408023525169
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I17cf3317b7b2b6657bbce9f29c59921a48ba172b
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/222645
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
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: 6e8093f565c9e39a3e40c285721c4f9c1de87905
  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!