[roll third_party/pigweed] roll: gn

From: git_revision:f284b6b47039a2d7edfcbfc51f52664f82b5a789
To: git_revision:b0c2742896b6b9f869dc0eb35ae4785cbf2a4512
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/209660
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: f8ccffa43290479..8fefe0c2a5a34c8
Roller-URL: https://ci.chromium.org/b/8748107309547657569
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I8b204d380294da419c7fcee89f737fd2085421e1
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209692
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
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: 9a89d7dc5768cb2bc4b4c8c1db243178d0802463
  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!