| commit | 0bbe2e72c3e7e5546610ebfd9c86ffeef268b8fb | [log] [tgz] |
|---|---|---|
| author | Wyatt Hepler <hepler@pigweed.infra.roller.google.com> | Tue Apr 16 21:49:11 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 16 21:49:11 2024 +0000 |
| tree | b632cd3b3a8d1967aea38ddf908fbcfe2741e7b2 | |
| parent | 2fd147a50b8d0f2f8ef4a7197e3171b375174ed7 [diff] |
[roll third_party/pigweed] pw_presubmit: Remove cmake_clang from quick presubmit cmake_clang is too slow for local presubmits. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/198050 https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 5c2f5153571a715..09c9355f6493ad0 Roller-URL: https://ci.chromium.org/b/8750464219272699585 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I876de7bea6bdea489ae01290fcd18e600863b0da Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/203990 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.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!