Google Git
Sign in
pigweed / pigweed / quickstart / bazel / fcf98356a6590e0b9879457498d84a91d064522c
commitfcf98356a6590e0b9879457498d84a91d064522c[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed May 08 22:08:10 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 08 22:08:10 2024 +0000
treeea6a2e75c78d275d4b83c8ad03ea022d76e9d493
parent2f67124c692d52422ca4af8d6c94e68fdab9e09b [diff]
[third_party/pigweed] Roll 4 commits

84853afa7c9be8e pw_bluetooth: Put cmake tests in modules group
5533f4333cf9f54 pw_format: Add Rust support for field width and ze
d9e14eb3cfffbe8 pw_i2c_mcuxpresso: Fix Clang compilation
bfccb2d8fb8e32f pw_bluetooth_proxy: Allow setting the # of credits

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 99192e42561f7d0..84853afa7c9be8e
Roller-URL: https://ci.chromium.org/b/8748469898267727585
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: If2194718bf7a2d17bef6f93508c35d758dd9a558
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209173
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: ea6a2e75c78d275d4b83c8ad03ea022d76e9d493
  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!