[third_party/pigweed] Roll 5 commits

9a0e93fe506c9f5 *: Replace `string_view&` with `string_view`
1e8d9d0656f836f docs: Add GitHub pull request template
abdcf98492e16e7 pw_spi_mcuxpresso: Rename flexspi to flexio_spi
1faa03a619f99f7 pw_spi_mcuxpresso: Fix Bazel build
9c2c92297a5165d pw_format: Add support for core::fmt style format

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: c8bdb2434d1efa8..9a0e93fe506c9f5
Roller-URL: https://ci.chromium.org/b/8749920300216893441
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I23145b8d06b96be5d71559a53a2b911ba7daa84f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/205852
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: b7333e0041fe586f191ca2bc1fe7f8faf3b969b6
  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/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!