| commit | bad1f79d6f3f9bfeab927bb1efdc25a85535c69d | [log] [tgz] |
|---|---|---|
| author | Wyatt Hepler <hepler@pigweed.infra.roller.google.com> | Thu Jun 27 07:20:07 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 27 07:20:07 2024 +0000 |
| tree | dafe3f1235d083982e8234df90f2c0caadf0c5f3 | |
| parent | 80588339252e6e312093a340b92f7bdbfc89e7fa [diff] |
roll: pigweed, pw_toolchain: pw_system: pw_system:async - Introduce a version of pw_system that uses async comms. - Add a pw_system example that uses a TCP port for comms. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/216239 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: edf7501f5d03e8f..befcb91b39880a5 Roller-URL: https://ci.chromium.org/b/8743995885328838497 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I388c97ccf2b462fec79e7f1ab7aff29b2d6268f9 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218458 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> 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!