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
When I was debugging the STM32F405 USB function, I encountered a crash.
It seemed that the data structure was damaged.
The cause of this problem is that the interrupt was responded to in the critical section.
This problem only occurred after I turned on the USB DEBUG function.
I found that in the syslog_putc function, different output functions are called according to the current calling context.
However, it does not handle the current situation in the critical section, resulting in task scheduling and interrupts being turned on in the critical section.
The text was updated successfully, but these errors were encountered:
@Virus-V maybe using RAMLOG as SYSLOG instead of SYSLOG over serial could help, them you just run dmesg later to see what happened.
Note: take care with using USB Trace, as Greg explained some years ago: when you add tracing you are changing the timing of USB and it could introduce issues.
When I was debugging the STM32F405 USB function, I encountered a crash.
It seemed that the data structure was damaged.
The cause of this problem is that the interrupt was responded to in the critical section.
This problem only occurred after I turned on the USB DEBUG function.
I found that in the
syslog_putc
function, different output functions are called according to the current calling context.However, it does not handle the current situation in the critical section, resulting in task scheduling and interrupts being turned on in the critical section.
The text was updated successfully, but these errors were encountered: