Google Git
Sign in
pigweed / pigweed / quickstart / gn / c5b5ed0d01f2edd6a33f6d2752c37bc120633e07
commitc5b5ed0d01f2edd6a33f6d2752c37bc120633e07[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Apr 23 00:54:24 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 23 00:54:24 2024 +0000
tree2c2ee19933ec520269e4e52e7e0a019472dc40df
parenta753aecda689fe93d8aea153178aa8169ad57358 [diff]
[third_party/pigweed] Roll 2 commits

682ac383f108edd emboss: Update emboss repo to tag v2024.0419.15560
b21f1b705dbf644 pw_web: Add user guide page for features and filte

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 9a0e93fe506c9f5..682ac383f108edd
Roller-URL: https://ci.chromium.org/b/8749908966315467713
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I783163ff7ae0dfb5cf083d1a7a0a184fb8b874b2
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/205854
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: 2c2ee19933ec520269e4e52e7e0a019472dc40df
  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!