Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 74a7ac3d37f8acb526e68e861ea0bfddf121d711
commit74a7ac3d37f8acb526e68e861ea0bfddf121d711[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Fri May 24 01:19:20 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri May 24 01:19:20 2024 +0000
tree798742d58dc6fc272a66f7025b28d6c2b34148a4
parent27d070ea514f2b399ceae52374cffa4b7446af3e [diff]
[third_party/pigweed] Roll 2 commits

8c1118fc91c259d rp2040: Renable tests that pass with larger stack
2ee9bbd280bae2f pw_web: Add split/resize view guide in docs

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: a90dc693295df7a..8c1118fc91c259d
Roller-URL: https://ci.chromium.org/b/8747098900432663793
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I1ab95f1f26dff69898e0f5f9af4f6bd22e4da14f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/211531
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 798742d58dc6fc272a66f7025b28d6c2b34148a4
  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!