[third_party/pigweed] Roll 5 commits

5cc356c68b27f7f pw_clock_tree_mcuxpresso: Remove unnecessary pw::
5b69003409b9ff3 pw_clock_tree_mcuxpresso: Add ClockMcuxpressoAudio
96a282aa6437950 pw_rpc: Add module metadata
13062c9ab277595 pw_router: Add module metadata
1dc0c0626a313f1 pw_varint: Add module metadata

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 243ba33cd5434c7..5cc356c68b27f7f
Roller-URL: https://ci.chromium.org/b/8745857210380000081
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I74fb0288d727cdcf49d5ede65b0d2440c3267ff5
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/214551
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: d47ff6e4016fcc16643f6af1fa6c0e29ffa5e033
  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. pigweed.json
  14. README.md
  15. requirements.in
  16. requirements_lock.txt
  17. 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!