Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 9b29a60e90f4bcaf328b71253ec92c873cc8f5bf
commit9b29a60e90f4bcaf328b71253ec92c873cc8f5bf[log] [tgz]
authorRob Mohr <mohrr@pigweed.infra.roller.google.com>Wed May 08 16:07:45 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 08 16:07:45 2024 +0000
treec847d627729896499c3e6bb62f42e017be312fb9
parentdb904c538c5028d044bbbfdeef4987397d08104c [diff]
[third_party/pigweed] Roll 2 commits

1409f882b06e9e5 OWNERS: Add roller as WORKSPACE owner
1b8054b032804a9 pw_presubmit: Exclude all OWNERS from copyright

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 258066a475ea2cf..1409f882b06e9e5
Roller-URL: https://ci.chromium.org/b/8748492560255414737
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ieb19352dc761c10c85e6f4979f7b98c79f1ce497
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209071
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: c847d627729896499c3e6bb62f42e017be312fb9
  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!