Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 0d8b613cd14497db0cbcae5f470fb9b6941d6ad2
commit0d8b613cd14497db0cbcae5f470fb9b6941d6ad2[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Apr 02 21:37:32 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 02 21:37:32 2024 +0000
tree8367b9d5830b45802c22b795ba009c10a359d13c
parent170ce04008b690a7a4035dd34bae5d38dfbbf7ce [diff]
[third_party/pigweed] Roll 2 commits

0540acc0b8bf0b1 pw_spi_linux: Move linux_spi from pw_spi to its ow
8a7744c250833e0 third_party/freertos: Fix typo in docs

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 0dafca3ccc0927b..0540acc0b8bf0b1
Roller-URL: https://ci.chromium.org/b/8751733294138179409
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I7c6e02f6c45b87b8e5bc3b223e1537fb1599f335
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/201612
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: 8367b9d5830b45802c22b795ba009c10a359d13c
  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!