[roll third_party/pigweed] roll: 310, 311

310
From: git_revision:29145e1bad586aa03beaa8cd1c4dbc602f28e6f1
To: git_revision:bb28159eee347b29eaa0628a005436040beba045

311
From: git_revision:29145e1bad586aa03beaa8cd1c4dbc602f28e6f1
To: git_revision:bb28159eee347b29eaa0628a005436040beba045
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/205230
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 4ab4b220f23f968..678e85847484879
Roller-URL: https://ci.chromium.org/b/8750078945575728161
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: If5a9f81b83ae3e30cf3aee37f3b287e2afffa9c5
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/205271
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: f10e68eb1f1c19042ae56a4e68649d2a3a579d8a
  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!