[wobble]

Hi.

Thanks for your reply. That is pretty much what I thought / found

You said “Do you get the ‘testing toolchain’ dialog? ” – No I don’t

You said “If no, try changing an arbitrary line on the Makefile Settings page (e.g. add a space to CFLAGS and remove it back) and clicking “Apply”.” – That’s exactly what I found that I have to do to get it to work. Is there anyway to make that automatic (i.e. when I change the user variable that is used in the Makefile Settings page)?

Thanks

[wobble]

Hi,

Thanks for getting back. Already tried using the “MemU32″ command. As stated in last post:

If I look at the memory via J-Link Commander (SEGGER software), the memory is correct.
In the GDB session window, the “MemU32″ command returns data is NOT correct (i.e. it’s the old value, not the new).
From your reply and these results, this indicates (to me) that the old values are getting cached at the GDB level.
Any ideas on how to stop this ‘cacheing’??

Thanks,

[wobble]

Hi,
Thanks for getting back. The command: “mon mem32” is not available in my GDB Session Window.
It is available from the J-Link Commander prompt (SEGGER software). If I look at the memory via J-Link Commander, the memory is correct. The PDF file that you sent me (section 5.11 “Command strings” details this).
In the GDB session window, the only command that appears to do what you suggested is the “MemU32” command (Full list of available commands returned via “mon help”). This returns the data at the address. When tried, this data is NOT correct (i.e. it’s the old value, not the new).
From your reply and these results, this indicates (to me) that the old values are getting cached at the GDB level.
Any ideas on how to stop this ‘cacheing’??

[Author]

Posts