Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 9fa470cd137de92161cb3ed2061080f02536056b
commit9fa470cd137de92161cb3ed2061080f02536056b[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jun 04 01:27:34 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jun 04 01:27:34 2024 +0000
treeca7314c955f6e0168d5898c8dc67e60b2ecde74b
parent1cc404f770eac7b65c0e475a607ff2a97176d521 [diff]
[third_party/pigweed] Roll 5 commits

80a5042814f199d pw_thread_freertos: Expand comment to help when de
9bed7bf6daedb3b pw_channel: Update function documentation
4cf2d05a70b44da pw_multibuf: Fix Truncate(0) on empty MultiBuf
fd77c2fe695697c docs: Add "skip to main content" a11y feature
f89935d35fb2da6 github: Fix step name

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 60ae08ad972b93b..80a5042814f199d
Roller-URL: https://ci.chromium.org/b/8746101800384459553
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I1bd7dd456a51b69739cb43437d6e67a4e4704938
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/213751
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: ca7314c955f6e0168d5898c8dc67e60b2ecde74b
  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!