Skip to content
This repository has been archived by the owner on Dec 18, 2023. It is now read-only.

USB not initialized does not trigger a fatal error #98

Open
gabryelreyes opened this issue Feb 15, 2023 · 0 comments
Open

USB not initialized does not trigger a fatal error #98

gabryelreyes opened this issue Feb 15, 2023 · 0 comments

Comments

@gabryelreyes
Copy link
Collaborator

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant