commit | 7e19b9700f4042854f10d53fe1b2a0e4dea2e017 | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Jun 06 21:16:07 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 06 21:16:07 2024 +0000 |
tree | 0fef4786dfd188874c8d0f02a8b98a72890584ae | |
parent | 034dd3d61968b520de6c00c2cf66a596ca9e08a9 [diff] |
[third_party/pigweed] Roll 5 commits 30abcad0910ff68 pw_android_toolchain: Add module metadata 732c882e8ec9bfd pw_async: Add module metadata 3fa03cadd9b06a1 pw_cli: Fish shell completion f4da9803f0e4e34 pw_presubmit: Add module metadata e202b0b771cd818 pw_sensor: Add Bazel support for Python package https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 5cc356c68b27f7f..30abcad0910ff68 Roller-URL: https://ci.chromium.org/b/8745845885803611553 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I3e320d133a85a0bcb2c79ba993924fd05bf0b427 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/214514 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!