Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 7877175e440118369fe2b2f3fb0f981545554f55
commit7877175e440118369fe2b2f3fb0f981545554f55[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Jul 10 23:54:07 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 10 23:54:07 2024 +0000
tree4ed0aabbeb72818dc5a817a2df04f7cbddae7eb7
parent5d8c75c9fdb253954312cdd6c9936c87238007e5 [diff]
roll: pigweed, pw_toolchain 3 commits

fa6e930113bd0e6 pw_presubmit: Narrow copyright notice exclusions
c16a0a5640a7649 dotfiles: Add copyright notice
1e211349047f0ad pw_log_string: Require backend_impl to be set expl

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 9c624cddf114a93..fa6e930113bd0e6
Roller-URL: https://ci.chromium.org/b/8742755968032107633
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I5f16a36af0b5384cb22e4886f6139f69f4abdf6d
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/221831
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: 4ed0aabbeb72818dc5a817a2df04f7cbddae7eb7
  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!