- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In TC27x controller After increasing the interrupt priority bootloader is going to trap. what is the register setting after increasing interrupt priority and what is the connection between increasing interrupt priority and trap?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
1. Please check the analyze the Trap reported with the Trap Class and TIN to know the cause of Trap.
2. Please check if it is due to a SW code issue or due to WDT overflow.
3. Since you mentioned that Interrupt priority increase caused the Trap please check if that ISR is blocking the tasks and/or not allowing the periodic servicing of the Internal/External WDG.
4. As mentioned in another comment, please refer to the Trap example on how to identify source of Trap and you could also monitor the call stack to see which function caused the Trap.
Regards,
Prudhvi.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Could you provide more details?
1. Which interrupt's priority is updated, leading to this? Could you share the interrupt configuration?
2. Could you share the working code snippet and the modified code snippet and what registers are changed?
3. You can refer to the example CPU_Trap_Recognition_1_KIT_TC275_LK-TR in ADS to understand the Trap class, Trap number, and how to identify the source of the trap.
4. You can refer to the call stack to find the instruction/access leading to the trap.
Best Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
1. Please check the analyze the Trap reported with the Trap Class and TIN to know the cause of Trap.
2. Please check if it is due to a SW code issue or due to WDT overflow.
3. Since you mentioned that Interrupt priority increase caused the Trap please check if that ISR is blocking the tasks and/or not allowing the periodic servicing of the Internal/External WDG.
4. As mentioned in another comment, please refer to the Trap example on how to identify source of Trap and you could also monitor the call stack to see which function caused the Trap.
Regards,
Prudhvi.