This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320F28335: Recommended SYSBIOS Illegal ISR (errorRaiseHook) settings for critical system

Part Number: TMS320F28335
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

  • Hi Wes,

    Our domain expert is out of the office at the moment, so she will respond in more detail when she returns next week.  In the meantime, please do provide a bit more clarity on your problem description.  The problem is being described as a CPU lock-up.  Do you suspect that it is due to an illegal ISR?  Are you able to connect to the target via CCS and see that it is at an illegal ISR?  It looks like you are on the right track with your debug, but please do provide us more information if you are still having problems.  You should see a response mid to late next week. 

    Thanks,

    Krishna