Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 762edee5b87ac68251e26caa62ad36cb7335b00b
commit762edee5b87ac68251e26caa62ad36cb7335b00b[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Sun Apr 21 21:54:05 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sun Apr 21 21:54:05 2024 +0000
tree1587110889b7f0784be127944a96a988889f696f
parent0e342568d8e69da3bb264fcd6a9b00d3ecca3199 [diff]
[roll third_party/pigweed] roll: gn

From: git_revision:415b3b19e094cd4b6982147693485df65037f942
To: git_revision:155c53952ec2dc324b0438ce5b9bd4a286577d25
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/205430
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 84084ec60dd5d15..0bfe65d4331f9ee
Roller-URL: https://ci.chromium.org/b/8750010964770098337
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I698aadab98e372b282705e350bedf401d2b89a70
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/205470
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: 1587110889b7f0784be127944a96a988889f696f
  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!