Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 06ab1110b6ac842ae429678feb28032795d54e6c
commit06ab1110b6ac842ae429678feb28032795d54e6c[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Apr 17 21:49:57 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Apr 17 21:49:57 2024 +0000
treeccc18698a71e17f282bb2c07c658534ce13420b1
parente3b3b8afc5695b8bbd02a58ef944b7c5331898d4 [diff]
[third_party/pigweed] Roll 5 commits

f3b08caf413b2a7 docs: Add pw_status table for API references
c4a939e113debc0 pw_bluetooth: Add versions - LEGetVendorCapabiliti
cf33fd5c9cc9b6f pw_bluetooth_sapphire: Iterators
a37b82ee271f61a many: Move maxDiff to be a class attribute
bb28159eee347b2 pw_sensor: Fix Python install

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: c779ef6691f3de7..f3b08caf413b2a7
Roller-URL: https://ci.chromium.org/b/8750373562759786689
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ib768c4f24fc810eddf5bc665e465a2c8bb90ea14
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/204271
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: ccc18698a71e17f282bb2c07c658534ce13420b1
  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!