Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 55ad0ad761c479f26445c524002be26e2330e430
commit55ad0ad761c479f26445c524002be26e2330e430[log] [tgz]
authorTaylor Cramer <cramertj@pigweed.infra.roller.google.com>Mon Apr 01 18:36:56 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Apr 01 18:36:56 2024 +0000
treea03f2c23c0bf649efa8a1c796ac2ae53d8cd949e
parent90a7c7847d80a15c52a97a1ccc6661ef9b9023c2 [diff]
[third_party/pigweed] Roll 2 commits

f50d5dcf8166a74 pw_hdlc: Document members of router
f37576a00cd3542 pw_channel: Return status from PollReadyToWrite

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 990b5f8ea0be1cc..f50d5dcf8166a74
Roller-URL: https://ci.chromium.org/b/8751835276312488097
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ib7330d919b16e1df0f6e2036af1f63a6a4680e1d
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/201255
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: a03f2c23c0bf649efa8a1c796ac2ae53d8cd949e
  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!