roll: pigweed, pw_toolchain 3 commits

dc7b7803aed532f pw_web: Change word-wrap to default true and save
65c56255b82a13c pw_system: Don't use implementation_deps
a55cfda13df756e pw_presubmit: Rename "misc" program to "sapphire"

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: f94f3f7299d8799..dc7b7803aed532f
Roller-URL: https://ci.chromium.org/b/8740773394070808433
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Iff2eb9615190c98a039c9ec629cabf2aa312ed6f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/227092
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 16e11ce89afbc85eac99a346c6a5576f4b8b5dbb
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  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!