Google Git
Sign in
pigweed / pigweed / quickstart / bazel / b3dd8f3f7ad26f1b06809f6439bcc95330f0e75a
commitb3dd8f3f7ad26f1b06809f6439bcc95330f0e75a[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jun 25 21:42:47 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jun 25 21:42:47 2024 +0000
treed0cf315d8cc15531fc9bb1a4be2344d7f9485779
parentf40ae8c705f1f1338a57abc1dea1bd4bf9c07d08 [diff]
roll: pigweed, pw_toolchain 4 commits

630750e177353d5 pw_cpu_exception_cortex_m: rm backend multiplexer
f437033232f7e9b bazel: Add clippy to CI
d1caa98c216d9f4 pw_build: Add optional working directory arg to Bu
74612309f33820a pw_log: Remove backend multiplexer

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 5880c31b48ea299..630750e177353d5
Roller-URL: https://ci.chromium.org/b/8744122819792714977
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I901f82b9b7086375be6705dc8124bd72f08a3c8a
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218254
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: d0cf315d8cc15531fc9bb1a4be2344d7f9485779
  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!