[third_party/pigweed] Roll 6 commits

28ee5c51dc16057 bazel: Move integration build config in-repo
fa03307ca0a1a92 pw_env_setup: Update clang next version
a31661c9795660c pw_clock_tree_mcuxpresso: Make Mclk and ClkIn depe
1aa7f44ecb7bf64 pw_clock_tree_mcuxpresso: Move example code out of
21277f94a062107 pw_clock_tree: Introduce ClockSourceNoOp class
65ba1ca17c9d57f pw_spi: Fix sitenav location for RP2040 backend

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 0f2537e5f13d9fd..28ee5c51dc16057
Roller-URL: https://ci.chromium.org/b/8746015862087432385
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ib47368579072f815252a40735b5b840e1f84e57a
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/214111
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: 2546f8cbbb15c9cd5b61ebeb4fa0bb0ea1ce8e0c
  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!