Google Git
Sign in
pigweed / pigweed / quickstart / gn / refs/heads/main
commit8ec9c646b6452ac02db224bac9f6bfaef1336690[log] [tgz]
authorRob Mohr <mohrr@google.com>Tue Apr 30 19:19:42 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 30 19:19:42 2024 +0000
treeda01d5c74d0b135de3ac750c63ddffd0e19edea3
parent63abe91d72670522b30627ae6a7dd366d2268f32 [diff]
github: Add basic on-push workflow

This workflow runs on Github. It currently fails, but it runs.

Bug: b/338083578
Change-Id: I50c26bb889b20c40d9d34016266b580a8fcc5394
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/207571
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Reviewed-by: Ted Pudlik <tpudlik@google.com>
Commit-Queue: Rob Mohr <mohrr@google.com>
1 file changed
tree: da01d5c74d0b135de3ac750c63ddffd0e19edea3
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  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!