Part Number:SECDEVTOOL-OMAPL138C6748
Hi everybody,
I am trying to write a DSP code using the PRUSS in secure-enabled OMAPL138 to load some ARM code to ARM Local RAM (or IRAM: 0xFFFF0000 - 0xFFFFFFFF), so that I can wake up ARM core at run time. I debugged that program using CCS and Texas Instruments XDS100v3 Debug Probe. However, during the debugging process, via using Memory Browser feature of CCS, I could not see the change of values in the region of IRAM as it must in my code. So I want to ask if the JTAG debugger has the right to access to IRAM to view memory?
I knew that the small ARM code had been already load to IRAM, because my ARM blinking led app did work properly. But now, on a much larger ARM image having no obvious sign of operation, I must check first that the IRAM is loaded with code and data before I jump to the entrypoint. If the IRAM is inaccessible to JTAG debugger, is there any alternative way to do the check?
I would be grateful for any help.
Best Regard.