Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 0647475b5960dc06dec83ee77700d7681956081d
commit0647475b5960dc06dec83ee77700d7681956081d[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Apr 24 21:55:51 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Apr 24 21:55:51 2024 +0000
treecdafc241c57482b694e61e27bce901b28a60d71c
parent444d420e0ca935a1012c7e64aa6e5c94b14cb053 [diff]
[third_party/pigweed] Roll 2 commits

f79f7c42e7921fe pw_tokenizer: Add DecodeOptionallyTokenizedData
82bbfff7ff83136 pw_sensors: Add support for triggers

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 96dee917b1ede10..f79f7c42e7921fe
Roller-URL: https://ci.chromium.org/b/8749739001012848145
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I13fc5f0b0247475c768f8f3599720f10119c6d39
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/206250
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: cdafc241c57482b694e61e27bce901b28a60d71c
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. README.md
  13. requirements.in
  14. requirements_lock.txt
  15. 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!