[roll third_party/pigweed] pw_assert_log: Fix Soong rules The the Soong pw_assert_log_defaults cc_defaults was incorrectly using pw_log_null as the log backend. This redirects all PW_LOG* calls to a no-op function, breaking PW_CHECK, PW_ASSERT and friends who depend on that. This would mean that code continued executing after a crash! Do not let defaults inject backends, especially the pw_log_null backend. Original-Bug: 324266698 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/190602 https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: bb1870ce1c8d99a..8b408829fcd8b9d Roller-URL: https://ci.chromium.org/b/8755970049054383745 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I4000851a838e2923aa770e67108b52d8b42e0616 Reviewed-on: https://pigweed-review.googlesource.com/c/example/echo/+/192784 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!