Google Git
Sign in
pigweed / pigweed / quickstart / bazel / e6b031468f71f73f3b342baa549e881b3fa2e017
commite6b031468f71f73f3b342baa549e881b3fa2e017[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon May 13 19:11:37 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon May 13 19:11:37 2024 +0000
tree3518955d090a206a9e99ab7b8cd6778382b2deed
parent074ec4fa4848921db8337597604376344de4db43 [diff]
[third_party/pigweed] Roll 2 commits

07f748073e5aa65 pw_unit_test: Add missing :config dependency for g
c004a95cf667642 pw_result: Fix typo in template member

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 8d2fdc5ed1aa017..07f748073e5aa65
Roller-URL: https://ci.chromium.org/b/8748027994687538049
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ic688209799c680dba811fa824b817a0f40cb9ef3
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/209700
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: 3518955d090a206a9e99ab7b8cd6778382b2deed
  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!