| commit | 15d9e82d1de65021cf65a2f94df3dce9051d44bf | [log] [tgz] |
|---|---|---|
| author | Jonathon Reinhart <jrreinhart@pigweed.infra.roller.google.com> | Mon Mar 31 13:32:32 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 31 13:32:32 2025 -0700 |
| tree | e5365bb97a93d5a9fa027bb43cad144a26624378 | |
| parent | 5d696ee31852481cb1b6d9358198b6ed348a9df9 [diff] |
roll: pigweed pw_console: Remove SO_REUSEPORT from SocketClient SO_REUSEPORT is intended [1] for load-balancing of TCP and UDP servers, not for the typical problem of re-opening a socket (due to TCP TIME_WAIT). Not only is SO_REUSEPORT inappropriate here, but recent kernels have started restricting [2] it to INET sockets, and attempts to set it on a UNIX domain socket now return EOPNOTSUPP, causing an exception here. * [1] https://man7.org/linux/man-pages/man7/socket.7.html * [2] https://github.com/torvalds/linux/commit/5b0af621c3f6ef9261cf6067812f2fd9943acb4b Test: Running 'pw console' works again on machines where this was crashing with "Operation not supported". Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/280332 Tests-Not-Needed: Jonathon Reinhart <jrreinhart@google.com> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Original-Revision: 90e30c56f1307574faeaec808a657e985fc872ae Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 6985a85e5cc6b0..90e30c56f13075 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8718850832557232625 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I7bd6ad4ec3fdecfd3ba73aced8cdcd95ab48bb6a Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/280412 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: 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 is a LED-blinking service (featuring RPC control!) for the Raspberry Pi Pico. It can also be run on any computer using the included simulator.
git clone https://pigweed.googlesource.com/pigweed/quickstart/bazel pw_bazel_quickstart cd pw_bazel_quickstart
The only dependency that must be installed is Bazelisk.
Bazelisk is a launcher for the Bazel build system that allows for easy management of multiple Bazel versions.
Instructions for installing Bazelisk can be found here.
To run the simulator, type: bazelisk run //apps/blinky:simulator_blinky Then, in a new console, connect to the simulator using: bazelisk run //apps/blinky:simulator_console
To start, connect a Raspberry Pi Pico, Pico 2, or debug probe via USB.
To run on the Raspberry Pi Pico, type: bazelisk run //apps/blinky:flash_rp2040 Then, in a new console, connect to the device using: bazelisk run //apps/blinky:rp2040_console
Once connected with a console, RPCs can be sent to control the LED. Try running:
device.set_led(True) device.set_led(False) device.toggle_led() device.blink(blink_count=3)
bazelisk test //... will run the unit tests defined in this project, such as the ones in modules/blinky/blinky_test.cc.
bazelisk run @pigweed//targets/rp2040/py:unit_test_server in one console followed by bazelisk test //... --config=rp2040 will also allow running the unit tests on-device.
Try poking around the codebase for inspiration about how Pigweed projects can be organized. Most of the relevant code in this quickstart (including RPC definitions) is inside modules/blinky, with some client-side Python code in tools/console.py.