Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 1cc404f770eac7b65c0e475a607ff2a97176d521
commit1cc404f770eac7b65c0e475a607ff2a97176d521[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Mon Jun 03 22:39:42 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jun 03 22:39:42 2024 +0000
treefc7e1c06585316fe4bdc7100c6be17d86f3921c1
parentc7fe00c26a29474bb3d643865d2eb273d3616d73 [diff]
[third_party/pigweed] Roll 4 commits

60ae08ad972b93b pw_channel: Remove manual registration from epoll
778137c3b26aea6 github: Add basic workflow and docs
ff81e38b61cc14b pw_containers: InlineVarLenEntryQueue::try_push()
aee408cfeb5522c targets/rp2040: Support running tests using the de

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 35450d745f54bdd..60ae08ad972b93b
Roller-URL: https://ci.chromium.org/b/8746113129617583345
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I9e1d9d7caa60e4c166da60295d4ec524b5cd49c1
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/213636
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: fc7e1c06585316fe4bdc7100c6be17d86f3921c1
  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!