Google Git
Sign in
pigweed / pigweed / quickstart / bazel / d0a5cded7a8b8b5b446f0d1d9e1d1a7f12061bc8
commitd0a5cded7a8b8b5b446f0d1d9e1d1a7f12061bc8[log] [tgz]
authorKevin Zeng <zengk@pigweed.infra.roller.google.com>Wed Jun 05 21:33:55 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jun 05 21:33:55 2024 +0000
treed9b42c51798ceaf56c032ff7d74abfc5eeee5367
parentb0a7c32027b67cc892116dd9a5d073731e540d63 [diff]
[roll third_party/pigweed] pw_multisink: Add option to inject a user defined lock

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/213211
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 52fa32ac0d460e0..28a9fb05372696b
Roller-URL: https://ci.chromium.org/b/8745935820325503505
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I7e5ab74b8081a38944e6b64a2e593986dbf13dfa
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/214192
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: d9b42c51798ceaf56c032ff7d74abfc5eeee5367
  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. pigweed.json
  14. README.md
  15. requirements.in
  16. requirements_lock.txt
  17. 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!