Customer environment is detailed below.
CCS Version: 5.1.1.00031TMS320F28022Signum JTAGjet emulator
Customer is observing that variable addresses and values are not matching up when displayed by the disassembly as well as the memory window. The attached jpeg files (in zip file) are screen captures illustrating this. In the example, the following is the expected address and data associated with the address.
Address Data0x3F43FE 0x5A5A0x3F43FF 0x0006
The customer wrote some code to set up a pointer to read the above memory locations and then view the results in the watch window in CCS. The results indicated the data is in fact in the correct, expected address locations.
Brandon
Brandon,
Unfortunately I don't have the exact hardware here (no Signum emulator, no F28022 card), but I can test on a card that is closer to the F28022 (I have a F28035) and try to see this behaviour with an example code. However, if I don't see anything do you think your customer could provide at least his .out file?
I'll let you know early next week if I can reproduce this issue here.
Regards,
Rafael
Try switching the page from "program" to "data" on the memory browser; in the upper left hand corner.
Thank you for looking into this. I will ask the customer for a test case, if needed.
For your information, the customer is using a Windows XP 32-bit machine.
Please check the attached screen; unfortunately I couldn't reproduce this issue here in my setup with the F28035 controlCARD connected to a DOCK board (thus XDS100v1).
Therefore it is difficult to imagine what may be happening in this case. If the customer is willing to send a testcase we can try to reproduce it here - although I am not sure if we will be able to get a F28022 device card, the F2803x devices should be close enough.
Cheers,
Reverting back to CCSv4 resulted in expected behavior. The same issue was not seen.
In this case I would suspect of something strange with their workspace or Debug configuration... If they are still willing to take a look at this issue, can you ask them to try a different workspace? If that works, then they could try to clean their existing one.
Details shown at the section General IDE of the CCS Troubleshooting page.