commit | c6d49a03c11c12ab53c47cea8aac4de50362e9ec | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Jun 05 00:13:38 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jun 05 00:13:38 2024 +0000 |
tree | 2546f8cbbb15c9cd5b61ebeb4fa0bb0ea1ce8e0c | |
parent | 65ef76f7049621262124f4d3bcff49b326ef5fd4 [diff] |
[third_party/pigweed] Roll 6 commits 28ee5c51dc16057 bazel: Move integration build config in-repo fa03307ca0a1a92 pw_env_setup: Update clang next version a31661c9795660c pw_clock_tree_mcuxpresso: Make Mclk and ClkIn depe 1aa7f44ecb7bf64 pw_clock_tree_mcuxpresso: Move example code out of 21277f94a062107 pw_clock_tree: Introduce ClockSourceNoOp class 65ba1ca17c9d57f pw_spi: Fix sitenav location for RP2040 backend https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 0f2537e5f13d9fd..28ee5c51dc16057 Roller-URL: https://ci.chromium.org/b/8746015862087432385 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ib47368579072f815252a40735b5b840e1f84e57a Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/214111 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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!