Google Git
Sign in
pigweed / pigweed / quickstart / bazel / d42578b38dc4fcf2e3179082fe61f481b75007a4
commitd42578b38dc4fcf2e3179082fe61f481b75007a4[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jul 16 22:17:56 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 16 22:17:56 2024 +0000
tree343eea559201f63ed0cb0463f52e140e84d54822
parentc62ab75a1d76b4e112ed77524a442af8d7c2518a [diff]
roll: pigweed, pw_toolchain 2 commits

07a9afe8a840ef9 pw_ide: Don't show root comp DB dir as target
0c7db655fb64de7 pw_result: Fix docs.rst example

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: b188ee240266da8..07a9afe8a840ef9
Roller-URL: https://ci.chromium.org/b/8742218047430124785
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I80150b6fa8b1e3d2435b9fdae1b23fcaea3b9ea6
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223535
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: 343eea559201f63ed0cb0463f52e140e84d54822
  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!