Google Git
Sign in
pigweed / pigweed / quickstart / bazel / f496d25cd63d4971539dc025985a5908ffc1a3ee
commitf496d25cd63d4971539dc025985a5908ffc1a3ee[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jun 18 18:29:36 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jun 18 18:29:36 2024 +0000
tree3345487151940f2ff4b8670564d56ab99d621f00
parentc6f121e71029438b2e2047c1285c2f6051d25b9d [diff]
roll: pw_toolchain, pw_toolchain 3 commits

42504afa03234e3 pw_docgen: Add bug Docutils role
3c319b21bb978db OWNERS: Add gwsq
67ea3940b6d3c0e pw_multibuf: Fix Android build

https://pigweed.googlesource.com/pigweed/pigweed
pw_toolchain, pw_toolchain Rolled-Commits: 3a1996034e63dea..42504afa03234e3
Roller-URL: https://ci.chromium.org/b/8744769428628475537
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I70e19a23953232b7402730bfbb5bf1d4a18ca9b7
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/216751
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: 3345487151940f2ff4b8670564d56ab99d621f00
  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!