I have an application on an STM32F205 that occasionally gives the above error in a pop-up on Crossworks. The "divide by zero" also appears in the status bar.
When it's done that, the application has usually halted in ctl_private_reschedule(), though that may just reflect that it spends much of its time there.
This looks to me like a problem with the debugger, but I certainly can't be sure of that.
I wondered whether anyone could shine any light on what's happening.
CrossWorks for ARM
I doubt it's relevant, but I'm chasing a problem where the USB on my target works fine with Linux host, but both USB data lines go high at the end of enumeration with Windows (8.1).
Please sign in to leave a comment.