Repository navigation
CI: compile usbhost into CircuitPython's ESP32-P4 DEV-KIT firmware, and say it has run there - #159
Merged
Merged
Conversation
…docs say the host has run there
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nothing in CI compiled usbhost's ESP32-P4 path on CircuitPython: the unix port builds it to nothing, so a change to the shared engine sources could break the board build with every check green. This adds a job that builds the WIFI6 DEV-KIT cell with usbhost and checks the engine's objects are linked.
The docs stop saying the host has never run on a CircuitPython board. On the WIFI6 DEV-KIT (host started with full_speed=True behind the onboard hub) it enumerated a Logitech C920e webcam (046d:08b6: video control and streaming interfaces, audio control and streaming) and an HP wireless keyboard-and-mouse dongle (03f0:5341: a boot keyboard and a boot mouse interface). usb.host.hid read the dongle's report descriptors (65 and 134 bytes), got boot protocol from GET_PROTOCOL, and held both interrupt-IN endpoints open for 75 s with no errors. No reports arrived, because nobody pressed a key or moved the mouse. The image was built from main after #158.