commit | 70e1fc28f90258a0e907667ec8c25e18b5a02051 | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Jun 05 18:14:39 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jun 05 18:14:39 2024 +0000 |
tree | 5a84f3da3d463d7ac50a8a6c692ddbfb0f953171 | |
parent | 1067e9c58f94e2683356d373cea5e0296967c918 [diff] |
[third_party/pigweed] Roll 3 commits 46a21c419e5561f bazel: No integration tests in wildcard build 83735047f7e90ed pw_transfer: Fix ConcurrentModificationException i 52fcc2ecdab0e05 pw_stream_uart_mcuxpresso: Make dma_stream Write o https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 04b802b31c9a0ca..46a21c419e5561f Roller-URL: https://ci.chromium.org/b/8745947871054198353 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I4a3cad3409df48e779a2ea1f8a3a19549c79de18 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/214191 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!