commit | 60e98963b33e7002b29e052745995f71ba8a27e3 | [log] [tgz] |
---|---|---|
author | Jonathon Reinhart <jrreinhart@pigweed.infra.roller.google.com> | Thu Aug 01 18:05:45 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 01 18:05:45 2024 +0000 |
tree | fa7a70a2c23da949c8265d27dd6382da6f685f23 | |
parent | 59497df355151c4d8a0a9b8750feb02926437ea9 [diff] |
roll: pigweed, pw_toolchain: pw_spi_mcuxpresso: Add SPI_RxError() and SPI_TxError() These are currently unused but are necessary for the FIFO overflow check in McuxpressoResponder::TransferComplete() which is currently disabled. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/226992 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: e51b311a154e11c..f94f3f7299d8799 Roller-URL: https://ci.chromium.org/b/8740784429226105409 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I9b2dad69c6e7fdb3f6aec54ea95ab2a64b14c06e Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/227091 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!