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
While configuring the USB driver using the InterruptExecutor model for multipriority execution, I noticed that the chip will lock up completely when the USB cable is inserted. The defmt trace logs from the device initialization appear to overwhelm the RTT buffer and cause a malfunction. I'll attach the full logs to this issue, but here are the final few lines (worth mentioning that it does always seem to fail at the same place):
<time> [TRACE] === status 01ec0080
<time> [TRACE] SETUP_DATA_RX
<time> [TRACE] === status 01e80000
<time> [TRACE] SETUP_DATA_DONE ep=0
<time> [TRACE] irq
<time> [TRACE] oepint
WARN probe_rs::session: Could not clear all hardware breakpoints: An ARM specific error occurred.
Caused by:
0: The debug probe encountered an error.
1: An error which is specific to the debug probe in use occurred.
2: USB error.
3: timed out
WARN probe_rs::session: Failed to deconfigure device during shutdown: Arm(Probe(ProbeSpecific(BoxedProbeError(Usb(Kind(TimedOut))))))
Error: An ARM specific error occurred.
Caused by:
0: The debug probe encountered an error.
1: An error which is specific to the debug probe in use occurred.
2: USB error.
3: timed out
System Info:
embassy-stm32 Features:
time-driver-any
defmt
stm32u575zi
memory-x
exti
embassy-usb Features:
defmt
While configuring the USB driver using the
InterruptExecutor
model for multipriority execution, I noticed that the chip will lock up completely when the USB cable is inserted. The defmt trace logs from the device initialization appear to overwhelm the RTT buffer and cause a malfunction. I'll attach the full logs to this issue, but here are the final few lines (worth mentioning that it does always seem to fail at the same place):usb-crash.log
The text was updated successfully, but these errors were encountered: