Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 860af4d0915541d8fe493f120dfc1109e3aa8a79
commit860af4d0915541d8fe493f120dfc1109e3aa8a79[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Mar 28 21:33:31 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Mar 28 21:33:31 2024 +0000
tree90d516805e5ab7dfbca350a80fd8ac3ba2571c5f
parent8de0345e4b646c92aa82b1075c871171cd0163dc [diff]
[third_party/pigweed] Roll 4 commits

0ee6ca26f6a11aa pw_presubmit: Refactor GN formatting support
ff16d3745ee4b50 pw_presubmit: Make ToolRunner capture stdout/stder
8531e52bc0e149d pw_emu: Fix a TypeError in TemporaryEmulator
6d2f01d2acec72e pw_module: Add OWNERS file during module creation

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: f05a8afb95aafdf..0ee6ca26f6a11aa
Roller-URL: https://ci.chromium.org/b/8752186529715617793
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I68feafa3b43a34a902f7c83fe571b42a3d5d296c
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/200905
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: 90d516805e5ab7dfbca350a80fd8ac3ba2571c5f
  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!