Google Git
Sign in
pigweed / pigweed / quickstart / bazel / cea53cc1a680d6a2f761bd75e0ffb334b584df8a
commitcea53cc1a680d6a2f761bd75e0ffb334b584df8a[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Tue Jul 16 19:10:09 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jul 16 19:10:09 2024 +0000
tree5d3cde108de134fa481a9792c296de6f46cd731c
parent8ee58da0207f474be9fa34f58b5d3d93c8ed060d [diff]
roll: pigweed, pw_toolchain 4 commits

f08c484d94d7f45 emboss: Update emboss repo to v2024.0716.040724
2eb848eb3c427a2 pw_presubmit: Add test for inclusive language chec
55dbd768bf62a1d docs: Minor updates
fc32542d40ea2a3 pw_assert_trap: Add a new assert backend which tra

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 81aad1379cb7f23..f08c484d94d7f45
Roller-URL: https://ci.chromium.org/b/8742229879855166449
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I8a09b64263d512c9ed136b59fa1b557cf26c4aa0
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/223554
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: 5d3cde108de134fa481a9792c296de6f46cd731c
  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!