You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2023. It is now read-only.
Current behaviour:
Error in the USB Driver does not trigger a fatal error and the system continues the initialization.
Expected behaviour:
Fatal error, and the system stops working.
Log
[D] Zumo32U4.cpp:1213 Resetting USB Host Shield now!
[D] Zumo32U4.cpp:1217 De-Registering ACM/CDC device instance now!
[D] Zumo32U4.cpp:1220 Fully re-set the USB HOST Shield and cleared ACM!
[E] Zumo32U4.cpp:1229 Could not initialize USB driver!
[E] System.cpp:168 Could not open the Zumo32U4 driver!
[D] System.cpp:175 Successfully started websocket API timeout service
[I] HTTPWebServer.cpp:79 Registered file serving route
[I] HTTPWebServer.cpp:82 Registered websocket API route
[D] System.cpp:188 HTTPs and WSS servers successfully started
[I] System.cpp:199 ++++++++++++++++ Done ++++++++++++++++
Issue found in PCB Number 1
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current behaviour:
Error in the USB Driver does not trigger a fatal error and the system continues the initialization.
Expected behaviour:
Fatal error, and the system stops working.
Log
Issue found in PCB Number 1
The text was updated successfully, but these errors were encountered: