| commit | b614538eca3f2af7d040907a9752e480d7cd7d43 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Mar 27 00:32:02 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 27 00:32:02 2024 +0000 |
| tree | f6bc3c3ad72c8448aa6246e69332d1b8d9eeda62 | |
| parent | ec35121e5bb9eeb2ca0b42ff38978d91222bdbfb [diff] |
[third_party/pigweed] Roll 11 commits 3473c9118a43845 pw_log_tokenized: Define as cc_static_library e0888f672378e3e pw_router: Define as cc_static_library 68e898711ea85b8 pw_toolchain: Define as cc_static_library df4efa0243b5dba pw_result: Define as cc_static_library 595fd9562a8d905 pw_build_info: Add log function of GNU build ID 6ebdfaf68c2e080 pw_span: Define as cc_static_library d99ef2cf38ae998 pw_preprocessor: Define as cc_static_library 04fbfa382513335 pw_bluetooth_sapphire: Add emulator start workflow e9441715b774fc7 pw_polyfill: Define as cc_static_library 5c53b840a4ecd3f pw_rpc_transport: Define as cc_static_library d6d27ec27a71859 pw_function: Define as cc_static_library https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: e0abef00c07545a..3473c9118a43845 Roller-URL: https://ci.chromium.org/b/8752356499968392513 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I6d4b375d497a5f779e20d733e9c2fdea86eeead5 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/200157 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/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!