Other Parts Discussed in Thread: SYSBIOS
Hello,
We need to diagnose as an interrupt when attempting to access the NULL address to read/write. How can we configure such an interrupt ?
Regards,
Bugra.
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.
Hello,
We need to diagnose as an interrupt when attempting to access the NULL address to read/write. How can we configure such an interrupt ?
Regards,
Bugra.
Hi,
There is no way to generate an interrupt when you try to access a NULL address (0x0000_0000). For other valid DSP memory addresses, there are MPU that can generate interrupt for invalid access: https://processors.wiki.ti.com/index.php/MemoryProtectionOnKeystoneDevices
Regards, Eric
lding said:Hi,
There is no way to generate an interrupt when you try to access a NULL address (0x0000_0000). For other valid DSP memory addresses, there are MPU that can generate interrupt for invalid access: https://processors.wiki.ti.com/index.php/MemoryProtectionOnKeystoneDevices
Regards, Eric
Hi,
Thanks for your quick response. It seems that the interrupt can be configured for the c6678 according to below forum item. So, is this something that applicable to c6678 but not c6671 ?
https://e2e.ti.com/support/legacy_forums/embedded/tirtos/f/355/t/229733?NULL-pointer-Exception
Regards,
Bugra.
Hi,
Sorry, I am not aware of this. C6678 and C6671 has the same C66x architecture, the same corepac, what worked on C6678 for exception handling should work as well on C6671.
Regards, Eric
lding said:Hi,
Sorry, I am not aware of this. C6678 and C6671 has the same C66x architecture, the same corepac, what worked on C6678 for exception handling should work as well on C6671.
Regards, Eric
Hi,
In the C6678 discussion I have mentioned above, an example was given for SYS/BIOS which is not applicable to our design since we use MicroC/OS-II, not SYS/BIOS. Could you please give me some examples or information on how we can configure such an interrupt (e.g. which interrupt event or system interrupt should be enabled).
Regards,
Bugra.
Hi,
I didn't find code for generating exception. Maybe you can refer to http://www.ti.com/lit/ug/sprugw0c/sprugw0c.pdf section 9.2.4 Exception Combiner. All the system events can be combined into exception.
Regards, Eric
lding said:Hi,
I didn't find code for generating exception. Maybe you can refer to http://www.ti.com/lit/ug/sprugw0c/sprugw0c.pdf section 9.2.4 Exception Combiner. All the system events can be combined into exception.
Regards, Eric
Hi,
I created this forum discussion after I had checked all 6671 manual documents including the document you have referred to anyway. I have tried lots of things to generate the null pointer exception interrupt but I couldn't.
Regards,
Bugra.
Hi,
In the referred E2E, it mentioned "I was able to now get an NULL pointer exception and it routes to the default exception handler which prints the CORE Pac register values on CCS debugger console." It seems to me that de-referencing a null pointer can cause an exception in SYSBIOS, is that working for you?
Regards, Eric