[third_party/pigweed] Roll 4 commits

312412b466c5118 pw_web: Capture browser logs in the log viewer
5ce9ca7349c2469 bootstrap: Warn about Windows case-sensitivity sup
f25eb6ab8c1d4cc pw_toolchain_bazel: Support Windows in toolchain t
6bbe3599f021969 docs: Clarify rvalue docs

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 25069b4047a57f3..312412b466c5118
Roller-URL: https://ci.chromium.org/b/8754716750859944593
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I723ddc4a0f7551b6d13f9eaa97e73e331dc6fc3f
Reviewed-on: https://pigweed-review.googlesource.com/c/example/echo/+/194722
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: fb89239bcb52267bf635fe193533320e4dda9fb8
  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/example/echo

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!