Google Git
Sign in
pigweed / pigweed / quickstart / bazel / ab030fccc55af4a7b8f1831cb265a2972193dc7c
commitab030fccc55af4a7b8f1831cb265a2972193dc7c[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Sun Aug 04 22:05:33 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sun Aug 04 22:05:33 2024 +0000
tree28cb7154833df231b6777b2471409387625169ad
parent535219e99c72b62abd99c8548c6911a6713700c3 [diff]
roll: pigweed, pw_toolchain 2 commits

71c4c844f102502 roll: gn
297f80e8180c0e0 roll: fuchsia_infra 119 commits

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 24a8258c6a77a3b..71c4c844f102502
Roller-URL: https://ci.chromium.org/b/8740497548058710849
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I5f56074362339f229848a899541140d40e8b6cca
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/227596
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 28cb7154833df231b6777b2471409387625169ad
  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!