Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 13fb0844169d4d8e018480ac53e7b03c669327b0
commit13fb0844169d4d8e018480ac53e7b03c669327b0[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Jul 31 18:47:52 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 31 18:47:52 2024 +0000
tree901f5830712d896dd14d065a961f013cd0624d25
parentd76fa0438c9323715013302c6ae176953555844c [diff]
roll: pigweed, pw_toolchain 2 commits

8f276075de78ca5 pw_web: NPM version bump to 0.0.21
116b67dbec88d7b bazel: Manage Java deps through bzlmod

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 9b9615e17801148..8f276075de78ca5
Roller-URL: https://ci.chromium.org/b/8740872309754437681
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Id21abfa32f3375bb965ba7fbfef7ce682a2c6048
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226892
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: 901f5830712d896dd14d065a961f013cd0624d25
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  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!