Rahul,
Yes, this is specifically just for debugging the secure binding process, I have not intention of exiting in SECUREWITHSK for the normal operational code.
Although I would ultimately like to debug the secure binding application, I first attempted to load and debug a much simpler application after exiting in SECUREWITHSK mode. This was also due to the fact that the secure binding application is DSP/BIOS-based and I still have some linking errors for the secure kernel in DSP/BIOS (mentioned in another thread).
This simple application tests the on-board mDDR RAM and therefore lives entirely in the internal RAM of the C6748. I am aware that there is a certain region of the internal RAM, which is off-limits during secure boot (0x0080 4000 to 0x0080 7FFF) and I have provided for this in the linker command file. I have attached the linker command and MAP files for some more information.
(Please visit the site to view this file)
(Please visit the site to view this file)
I would have to investigate the possibility for some interrupt being set at that point. As far as this application is concerned, only the Timer2 and UART0 interrupts are enabled, but the program runs into the weeds before these interrupts are even configured. It might be some exception?