[third_party/pigweed] Roll 4 commits

807b25704367768 bazel: Remove unnecessary .bazelrc flag
55a0e49ae0aae5d pw_build_mcuxpresso: Support multiple cores
4f238babeb357b7 pw_sys_io_stdio: Expand allowed uses beyond host
d60a7315d676b9d bazel: Re-enable sandbox_hermetic_tmp

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 15660a9a2d0102e..807b25704367768
Roller-URL: https://ci.chromium.org/b/8748639872677864225
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I27ba3ebb5d43e8c1d711ed755617c5d4716ddcb5
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/208573
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: dc4bfdb2fcfe7132ff6e7c8a5e7653d4d5b065e8
  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!