Google Git
Sign in
pigweed / pigweed / quickstart / bazel / b5e438eaa3b81a451685ad577c7e6194aa64593e
commitb5e438eaa3b81a451685ad577c7e6194aa64593e[log] [tgz]
authorWenji Li <wenjili@pigweed.infra.roller.google.com>Tue Apr 02 03:36:53 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 02 03:36:53 2024 +0000
tree534352abdc33dc93207765611dde37434bbc8c16
parent878eead5bd80c768458d9ff98cfa15fa9b1f44cc [diff]
[roll third_party/pigweed] SEED-0126: Claim SEED number

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/200911

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 035f292d35a6918..4f049a2e95df9ca
Roller-URL: https://ci.chromium.org/b/8751801282404287953
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I016c78f96dae74673afb114649d08653334a0e78
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/201412
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: 534352abdc33dc93207765611dde37434bbc8c16
  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!