Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 8de0345e4b646c92aa82b1075c871171cd0163dc
commit8de0345e4b646c92aa82b1075c871171cd0163dc[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Mar 28 18:33:25 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Mar 28 18:33:25 2024 +0000
tree1ac2e9e2ea44c8a2c189438034752e7ec36ff748
parent9cb159e1867f7c318c6395e20c1590ffb29c0511 [diff]
[third_party/pigweed] Roll 5 commits

f05a8afb95aafdf SEED-0117: Update status to Last Call
a0fec21f46ee751 third_party/fuchsia: Copybara import
3e8bef930da69af nanopb: Fix nanopb_pb2.py generation
6d7b236a2fe4be1 pw_web: Fix logs not appearing in pw_console serve
273fa7962c10e83 pw_bluetooth: Emboss formatting tweak

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: b8c700540dbb7c0..f05a8afb95aafdf
Roller-URL: https://ci.chromium.org/b/8752197860231603281
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: If27c370f39e3d02d2c0ab3e88fa3e6eba24c59e8
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/200899
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: 1ac2e9e2ea44c8a2c189438034752e7ec36ff748
  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!