Memory browser vs mem command with Debugger Shell

klm78 — Tue, 20 Sep 2011 23:22:03 GMT

Hi,

We have some doubt concerning the memory browser window in CW 10.1.8 for StarCore.

Our Configuration is ADS8156

If we open this browser at a memory adress in DDR > 0x40000000 and look at the same adress with Debugger Shell mem command

The result is the same.

If we modify a value memory cell in the browser, there's no change observed with mem command in Debugger Shell

Which way is the most accurate for dumping memory in Debug Mode ?

Is this issue could be due to CACHE management ?

Thanks in advance

BR. klm78

Re: Memory browser vs mem command with Debugger Shell

Daniel_Popa — Thu, 22 Sep 2011 00:25:43 GMT

Hi klm78,

Seems to be indeed a cache related behavior. I'll check this and return with details as soon as I'll have access to a board.

Nonetheless, the preferred way of dumping memory are Target Tasks/Import-Export memory.

Also, please be aware that there are two types of Memory views supported in CW - one of them is the Memory Browser view with a reduce set of features and the other one is Memory view.

I advice you to use the Memory view, where you can place a monitor (for example at 0x40000000) and in the same time you can specify which type of memory is used (physical, virtual for data or virtual for program)

Hope this helps.

CodeWarrior for StarCore中的主题 Memory browser vs mem command with Debugger Shell

Memory browser vs mem command with Debugger Shell

Re: Memory browser vs mem command with Debugger Shell