Google Git
Sign in
pigweed / pigweed / quickstart / bazel / bf16a592e7b165d0bc3ff0b95af1a01b85c841fb
commitbf16a592e7b165d0bc3ff0b95af1a01b85c841fb[log] [tgz]
authorDavid Rees <drees@pigweed.infra.roller.google.com>Wed Apr 24 03:55:37 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Apr 24 03:55:37 2024 +0000
treee80ed0da249787e9a04f65175b9d2a385b9a43d7
parentce72a15a4d9604b7e2d50fafbd7f6c3418477013 [diff]
[third_party/pigweed] Roll 2 commits

e7fc5d241ad4508 pw_bluetooth_proxy: Fix ordering of TEST arguments
314a7b9bfa1e540 pw_bluetooth: Comment why we include all emboss he

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: a5052ba92950982..e7fc5d241ad4508
Roller-URL: https://ci.chromium.org/b/8749806984765799425
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Id77ff7f0f764bb8db4a68595181ba19e772a7196
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/205972
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: e80ed0da249787e9a04f65175b9d2a385b9a43d7
  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!