Google Git
Sign in
pigweed / pigweed / quickstart / gn / dec91f4b90e2b7f95bcfcc5b07e64eaa535c9f89
commitdec91f4b90e2b7f95bcfcc5b07e64eaa535c9f89[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Thu Apr 25 21:56:41 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 25 21:56:41 2024 +0000
tree866da0cdca9bb44285d7922a1b6e241613326a62
parent3bc0f7a7e9e8ab53f5fb75d976735625a39c6389 [diff]
[third_party/pigweed] Roll 3 commits

a56e966f863779b pw_build: Fix using pw_cc_blob_library target in e
de74460373ec62a pw_string: Add ToString for iterables
cda2a749853a894 SEED-0128: Claim SEED number

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 1807af542686e6d..a56e966f863779b
Roller-URL: https://ci.chromium.org/b/8749648350385823985
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I06eafecd7f625d15deba683ac9f71335d1125fac
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/206750
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: 866da0cdca9bb44285d7922a1b6e241613326a62
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. README.md
  13. requirements.in
  14. requirements_lock.txt
  15. 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!