Google Git
Sign in
pigweed / pigweed / quickstart / bazel / c20f045bb44d04de186b0c42d2f4422c0ceaade4
commitc20f045bb44d04de186b0c42d2f4422c0ceaade4[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jun 18 03:42:45 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jun 18 03:42:45 2024 +0000
tree05624fd8395185aa58f96511d0dfff4ab465c6fa
parent455f619916bfa6f0bf732676de87c0fcdd8412a9 [diff]
roll: pw_toolchain, pw_toolchain 4 commits

2304e6ebc21e39b third_party/pico_sdk: Fix exception names in GN bu
5496bcf12266a83 docs: Update Pigweed Live schedule
2ed9c5a80eeb76d pw_system: Allow disabling of DeviceTracing RPC ca
5f36f8db6dcbb70 docs: Bazel compatibility patterns

https://pigweed.googlesource.com/pigweed/pigweed
pw_toolchain, pw_toolchain Rolled-Commits: b0cdbe138ff4623..2304e6ebc21e39b
Roller-URL: https://ci.chromium.org/b/8744826082960062417
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I4bb5c33d9487443e3bac2193964b67e52ca0f463
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/216109
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: 05624fd8395185aa58f96511d0dfff4ab465c6fa
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. BUILD.bazel
  9. echo.bzl
  10. LICENSE
  11. pigweed.json
  12. README.md
  13. requirements.in
  14. requirements_lock.txt
  15. 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!