| commit | e988d12cf060522694e796dc019e62d523da9ca1 | [log] [tgz] |
|---|---|---|
| author | Jonathon Reinhart <jrreinhart@pigweed.infra.roller.google.com> | Tue May 21 16:17:32 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 21 16:17:32 2024 +0000 |
| tree | 75e3bc56dc1db3f16c882bb00536451b664600bc | |
| parent | 8cabe6a97ad4d63fc24846f59623a93f8242f7e5 [diff] |
[roll third_party/pigweed] pw_spi_mcuxpresso: Remove unnecessary debug messages These were helpful during development but are no longer useful. Also remove now unsued "state" accessors. Test: Build and test in downstream project Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/210711 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 4d84714f44de7d6..ea9a81f748e5b60 Roller-URL: https://ci.chromium.org/b/8747314178731017137 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I25ee63e569c31ebe9b35e6a7f7879b1a16ada013 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210751 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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!