Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 643d83ed8203c2d7464909063cff3114ea84153e
commit643d83ed8203c2d7464909063cff3114ea84153e[log] [tgz]
authorEric Rahm <erahm@pigweed.infra.roller.google.com>Sat May 04 04:04:00 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat May 04 04:04:00 2024 +0000
tree9ebcb21982044cbf799e5bbbb832f721a8992dc1
parent061023c7db8c405b45827b5d2d87b7f0c2cf307e [diff]
[third_party/pigweed] Roll 2 commits

178dee4d673a285 emboss: Update emboss repo to tag v2024.0501.21542
33da8827caa5441 pw_package: Suppress package progress messages

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 6c158d179f8e53b..178dee4d673a285
Roller-URL: https://ci.chromium.org/b/8748900481839450049
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: If039f1623ba606e124e9434a130890943ab9e20d
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/208392
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
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: 9ebcb21982044cbf799e5bbbb832f721a8992dc1
  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!