CCS5 memory content after connecting target

Hi HR,

HRi said:

I cant read the memory I'm getting "----" instead of the memory content, the memory map looks good

usually the "----" indicates that the debugger is blocked from reading that memory location because of the debugger memory map. You said the map looks good. Do you mean the debugger memory map (instead of the memory map file)? Did you confirm that the debugger memory map has that memory region defined as readable?

HRi said:

I'm using CCSv5.2.0.00069 under windows XP, I have CCS3.3 installed on the same machine and it is working fine, what could be the issue?

Usually the inconsistencies between the two versions is a difference in the GEL startup file being used. I would make sure that the same (or similar) gel files are being used (note that some CCSv3 GEL actions related to projects and the GUI are not supported in v5)

Thanks

ki