[third_party/pigweed] Roll 12 commits

ff21b928c01c169 pw_build: Add pw_elf_to_dump rule
ee4eea8fda11b8d pw_digital_io_linux: Add trigger option to CLI wat
eee966337afe905 pw_log: Cast log level to int32_t
962d662171f05d0 pw_transfer: Always terminate transfers on stream
66c06bc9f876fc1 docs: blog: Bazel feature flags
7a6837d6e7ca33d pw_digital_io_linux: Add "watch" command
1ed69ae399e31f7 pw_digital_io_linux: Add support for input interru
e56d63cfa56952f pw_digital_io_linux: Move examples out to compiled
2fd1e9cc714a565 pw_digital_io_linux: Update mock_vfs
a07f9d1b43ebf67 pw_digital_io_linux: Add log_errno.h
9e5f85b2ed9593a pw_system: Mention that extra libs need alwayslink
96313b7cc138b0c pw_malloc: Add allocator backends

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 93fa287dc5010cf..ff21b928c01c169
Roller-URL: https://ci.chromium.org/b/8746373722770720577
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ic7955d9b56601b42f37fa85ec6281d5ea0c6f87a
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/213191
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: 73f1776431245be7086dab2b4710ba68216951e7
  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!