Google Git
Sign in
pigweed / pigweed / quickstart / gn / efa4a69b3d831fc0ca0240a9efaaf70d539927d3
commitefa4a69b3d831fc0ca0240a9efaaf70d539927d3[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Apr 30 01:00:13 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 30 01:00:13 2024 +0000
tree8d8d4b7ccbc435a5fcf94e372aa574b56fc9ab53
parentee1ee69019049d37e29cb6c686ef04a1652298bb [diff]
[third_party/pigweed] Roll 3 commits

33d6d7e04508964 pw_bluetooth: Add LoopbackCommandEvent
189b54cf33ff8e2 *: Run clang-format
53be9f9c6724a4f pw_bluetooth: Support Read RSSI command and event

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: fa1938a64124d21..33d6d7e04508964
Roller-URL: https://ci.chromium.org/b/8749274423447210865
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: If4ea8d26321c27d8a9d88711ec008b7c849c0c5d
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/207392
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 8d8d4b7ccbc435a5fcf94e372aa574b56fc9ab53
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. README.md
  13. requirements.in
  14. requirements_lock.txt
  15. 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!