[third_party/pigweed] Roll 2 commits cf062ce10841003 pw_rpc_transport: Add log for no packet available 58e754ea92e9ed8 pw_stream_uart_mcuxpresso: Fix code examples in do https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: f4e6db77b1ae6c0..cf062ce10841003 Roller-URL: https://ci.chromium.org/b/8754807389415981137 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I6c7e4a040217bccfcc3cb72706440d39421af183 Reviewed-on: https://pigweed-review.googlesource.com/c/example/echo/+/194623 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/example/echo
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!