Google Git
Sign in
pigweed / pigweed / quickstart / bazel / d76fa0438c9323715013302c6ae176953555844c
commitd76fa0438c9323715013302c6ae176953555844c[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Jul 31 18:42:14 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 31 18:42:14 2024 +0000
tree6745da0cbb1588bb9d66ab347689eae80b0bcdb7
parente21ae3592d5e30ea047cff52ec43ed1362c03581 [diff]
roll: pigweed, pw_toolchain 5 commits

9b9615e17801148 pw_presubmit: Add new presubmit steps
285805a35a9878a pw_web: Enable custom titles, log-view access
71a9d5447de318e docs: Fix some bad links in the changelog
40caf32b68cf760 third_party/stm32cube: bzlmod-friendly changes
df07efa092d4072 pw_rpc: Add yield mode constraint_setting

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: b454ef6a4541f4f..9b9615e17801148
Roller-URL: https://ci.chromium.org/b/8740872708181800913
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I6cda41945bfbf36aae4377814c257c7c6ecef632
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226852
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: 6745da0cbb1588bb9d66ab347689eae80b0bcdb7
  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!