[third_party/pigweed] Roll 3 commits

9c7d87957171705 pw_unit_test: Ensure alignment of test fixtures
969c75d77d2fbcf pw_transfer: Fix transfer_thread_test initializati
2e46e4ac3dfbbfc pw_config_loader: Remove unnecessary dep

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 1edf35a4ff1c563..9c7d87957171705
Roller-URL: https://ci.chromium.org/b/8747654085648819857
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I31f5cb87997ec4aef69c9da86dc8bd0d6094c5f8
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210359
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: a777a430252276ecb5f73fa12228a45a0f52a521
  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!