Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 2ddff182c36169b07a8b3000e683a0fe51d6db87
commit2ddff182c36169b07a8b3000e683a0fe51d6db87[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri Jul 12 02:42:33 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jul 12 02:42:33 2024 +0000
tree0872bcb97e6eb4c47b56f6df0fd725acce29b011
parent3812d07bc6aefbca165d7ac08f2bf46e7ffe1e95 [diff]
roll: pigweed, pw_toolchain 3 commits

bf88de9f5c04467 pw_system: Reusable DeviceConnection functionality
ada3a6bb4f662b4 pw_web: Add filter field buttons and placeholder
db01bc93c1a3857 pw_web: Include core .proto files in the npm bundl

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: a047c412171136c..bf88de9f5c04467
Roller-URL: https://ci.chromium.org/b/8742654391957605569
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I08203eb7b9c7dbfd6b432c344dfaf870a2091bfe
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/222638
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: 0872bcb97e6eb4c47b56f6df0fd725acce29b011
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  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!