Google Git
Sign in
pigweed / pigweed / quickstart / bazel / b6ff14c87854629448bb96825cde98b9e34998e3
commitb6ff14c87854629448bb96825cde98b9e34998e3[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu May 02 04:04:31 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu May 02 04:04:31 2024 +0000
tree0ff9d8f38028747ee9d7786cab1e8aee96ff4104
parent7285b9c27898e3d8519dae112e238124d8a5dee1 [diff]
[third_party/pigweed] Roll 2 commits

aa19504faca0b72 pw_web: Fix font colors in packaged version
31875b799730ab1 pw_toolchain: Register ARM m33 toolchains

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 58a09c188df0cc6..aa19504faca0b72
Roller-URL: https://ci.chromium.org/b/8749081793337405777
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ia394b2acb428779e723245475db2bdc11dc356d4
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/207586
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
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: 0ff9d8f38028747ee9d7786cab1e8aee96ff4104
  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!