Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 06acc10b9fdb33cc2e5fbe677084ee3fe3760415
commit06acc10b9fdb33cc2e5fbe677084ee3fe3760415[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed May 22 01:17:53 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 22 01:17:53 2024 +0000
tree76e6c2d2af4e76d162eb2ba34302a8a2ee908824
parenta08505f4d9b01412f908d0e6a2232565c22bcf9f [diff]
[third_party/pigweed] Roll 4 commits

506466d72aa5cbf pw_channel: Consistent datagram/byte channel alias
cd15ca3178ec45e pw_allocator: Track requested sizes in blocks
cae40e3337b2234 pw_toolchain: Add clang-apply-replacements plugin
a2504dc03eab921 targets/rp2040: Allow using rp2040 devices in boot

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: f86d3492dd95f8b..506466d72aa5cbf
Roller-URL: https://ci.chromium.org/b/8747280183513490545
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I3b1a38e30e6f48effe160935da35b9bad52e24a8
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210837
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 76e6c2d2af4e76d162eb2ba34302a8a2ee908824
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  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!