Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 634ecf1d4566a8b4dc5056dad69b42ed709d452c
commit634ecf1d4566a8b4dc5056dad69b42ed709d452c[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue May 28 19:22:51 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue May 28 19:22:51 2024 +0000
tree198aa2d611bc1aedbe243c7df7a800efeb65af95
parenta4fb0d715bda2df50a2d0a32871c1a0da3db269e [diff]
[third_party/pigweed] Roll 3 commits

eb97b4508f6e0ca rp2040: Add upstream Bazel platform definition
c932087017d7024 pw_cpu_exception_cortex_m: Fix incorrect inputs to
c71207f85e160f4 pw_allocator: Fix Android build

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