[roll third_party/pigweed] roll: gn

From: git_revision:0a2b8eac80f164f10b2cbc126890db0d295790cd
To: git_revision:03d10f1657b4ddace618c34ab61b6357d1ae9c9a
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/193850
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 7a9b71ad0a5436e..154897dd5f6d239
Roller-URL: https://ci.chromium.org/b/8755079322163112449
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I283c54e92994d1224e1288740e98b06a9b1f4e63
Reviewed-on: https://pigweed-review.googlesource.com/c/example/echo/+/193871
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: 18f75970fd186bd9c6df6b4817a0926b295715a4
  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/example/echo

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!