Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 5dacba556401fd53eb79b6d6867e6244c627ff13
commit5dacba556401fd53eb79b6d6867e6244c627ff13[log] [tgz]
authorKayce Basques <kayce@pigweed.infra.roller.google.com>Fri Jun 07 00:27:19 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jun 07 00:27:19 2024 +0000
tree28a63a7dd7336284d24e6e829ed39d000527a158
parentfec96c3b1ab00137c90954b25a99ac1bf005263c [diff]
[third_party/pigweed] Roll 4 commits

1d82b0ff4c571fe pw_uart: Add module metadata
ec741c8c94303ff pw_build_mcuxpresso: Add module metadata
03d0423f7f196c8 pw_analog: Add module metadata
8d296361c1f6074 pw_base64: Add module metadata

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 9ea9ef130481b82..1d82b0ff4c571fe
Roller-URL: https://ci.chromium.org/b/8745834546835330769
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Id34a6555260387b28eeebff9254e5cc989b04ad5
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/214557
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: 28a63a7dd7336284d24e6e829ed39d000527a158
  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. pigweed.json
  14. README.md
  15. requirements.in
  16. requirements_lock.txt
  17. 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!