Google Git
Sign in
pigweed / pigweed / quickstart / bazel / be797c06087b8a05ebf8984a7e01e009de78e334
commitbe797c06087b8a05ebf8984a7e01e009de78e334[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Apr 12 22:00:07 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Apr 12 22:00:07 2024 +0000
tree7710259eed374d1d2dca9cba49e33b077bd03b63
parent4bce88a8cb282e9ecb32d36ad64c6609abbabd48 [diff]
[third_party/pigweed] Roll 3 commits

57d41af75d9459d pw_spi_linux: Add pw_spi_linux_cli
6d332ab9dbf286a pw_allocator: Add Pool
c47f14d48c690fd pw_allocator: Update OWNERS

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 9375570a863aa43..57d41af75d9459d
Roller-URL: https://ci.chromium.org/b/8750826823357359201
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ib1f5bbd5f99546373e33ee40ab932d472e358c3d
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/203272
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: 7710259eed374d1d2dca9cba49e33b077bd03b63
  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!