Memory browser shows question marks after a while

Hello,

The question marks usually refer to a memory address that does not exist on the target. What address are you attempting to access (and on what page)? What emulator are you using?

Thanks

ki

Hi,

This behaviour occurs on random memory addresses on page1. I.e. before the question marks show up, debugging works fine. I use the XDS100 emulator.

You mentioned that you believe the connection with the debugger is lost. If that is the case, your should see the status say it is disconnected in the Debug view. Can you confirm that is what you see? If there is a disconnection, the memory view should become grey also.

A screenshot would be useful also.

Thanks

ki

I have added a screenshot of the situation. I don't see somthing that says disconnected.

3060.screenshot ccs5.doc

You are indeed connected, running, and in real-time mode with continuous refresh enabled in the memory view. That should work. If you pause the target, do you see any valid data in the memory view?

We tried to pause the target but without success.

Did you have any progress finding regarding this problem? We have the idea that scrolling in the memory browser sometimes triggers the error situation.

3603.debug_server_log.log

Please find the attached log file of the error situation.

Hi Roland,

This might be because you are using a slower emulator. Could you please try changing the Continuous refresh interval to something larger say 2000 ms from the default 500 ms and see if it helps. You can access the option from the preferences dialog. Under Code Composer Studio -> Debug , look for Continous refresh interval (milliseconds) and set it to 2000.

Regards,
Mandeep 

Thanks for the suggestion. However, I still have the problem (see attached log)

0755.ccs.log

Roland,

Did you close the memory browser and restart the debug session after updating the preference. Also, did you notice the actual refresh rate of the memory browser change after applying the changes.

Regards,

Mandeep deol

Ronald,

Could you please try setting the refresh interval to be even longer say 4000 ms.

Mandeep

Hi Mandeep,

This doesn't help. When in the error situation, pressing the pause button and step through the code works. Only the memory browser 'hangs' (shows questionmarks).

Best regards,

Ronald