Other Parts Discussed in Thread: SYSBIOS
Hi everyone,
My team is trying to determine an issue in our electronics / firmware regarding a CPU lock-up. One area that we are investigating is a possible illegal ISR occurring between our custom bootloader jumping to our SYSBIOS application. Previously we left the Illegal ISR to the default used with SYSBIOS and did not set an errorRaiseHook. We would like to set this to clear all the interrupt flags to see if this gets us past a CPU lock-up issue that we are seeing with some new electronics. Perhaps, even better would be a way to disable or at least indicate the particular interrupt that caused the illegal ISR to occur. I expect to do this on both our custom bootloader and our SYSBIOS application. This may not help our CPU lock-up issue, but we'd like to firm up this area of our application.
Any help is appreciated. Thanks,
Wes