| commit | 285f70032c52b4b6c14b5879fa460823b972d715 | [log] [tgz] |
|---|---|---|
| author | Alexei Frolov <frolv@pigweed.infra.roller.google.com> | Thu May 30 01:24:09 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 30 01:24:09 2024 +0000 |
| tree | 82c68a8a3865a9b23876cb5d0c96edf0923eba15 | |
| parent | d6dec29200285b8f4b9f5ae5ba4cb79da2aebae8 [diff] |
[roll third_party/pigweed] pw_channel: Add EpollChannel This implements a pw::channel::Channel which sends and receives data through a file descriptor, with read and write notifications backed by Linux's epoll system. To facilitate this, several additional APIs are added to the epoll async2 dispatcher, allowing registration of additional file descriptors. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/210813 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 3763a9d5b54c766..e07a08914d79ea1 Roller-URL: https://ci.chromium.org/b/8746555022131683777 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I8334b68784007db998b1dec6be83e444f4225368 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/212097 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!