Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 170ce04008b690a7a4035dd34bae5d38dfbbf7ce
commit170ce04008b690a7a4035dd34bae5d38dfbbf7ce[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Apr 02 18:37:17 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 02 18:37:17 2024 +0000
tree2bf721ef06f50785ab054a37a06bd0cd8cae9a12
parent065a58c70bd68ba27ac1f1b2934776a0ca4f16b2 [diff]
[third_party/pigweed] Roll 2 commits

0dafca3ccc0927b SEED: Reading sensor data
4aa0252e35b34be pw_result: Avoid duplicate symbols with Soong

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 30f64d3eedfbd31..0dafca3ccc0927b
Roller-URL: https://ci.chromium.org/b/8751744628877966833
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ibc183aaa90befdb0d80d6db1f72b74cecf35c13f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/201552
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: 2bf721ef06f50785ab054a37a06bd0cd8cae9a12
  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!