| commit | c6f121e71029438b2e2047c1285c2f6051d25b9d | [log] [tgz] |
|---|---|---|
| author | Kayce Basques <kayce@pigweed.infra.roller.google.com> | Tue Jun 18 03:52:07 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 18 03:52:07 2024 +0000 |
| tree | a82f6900888f6b9c82c290c468678dec217072ee | |
| parent | 81840033034d70eee581a68892398a95e727421c [diff] |
roll: pw_toolchain, pw_toolchain: docs: Update GitHub actions tutorial Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/216276 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pw_toolchain, pw_toolchain Rolled-Commits: 6411cd88cf8cd7c..3a1996034e63dea Roller-URL: https://ci.chromium.org/b/8744824348354588705 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I6e2b30c27ab95509ce71a91d070aa12b28917f15 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/216571 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>
This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.
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.
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
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.
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!