|ARM Technical Support Knowledge Articles|
Applies to: ULINK USB-JTAG Debugger
Information in this article applies to:
I have moved some constants into a different memory area (in my case an external Flash). Now, I am getting a memory mismatch when the debugger starts.
However, during Flash programming (which was just executed before) everything was OK. What can be the reason for my problem?
By default, on debugger start a CPU reset is issued and the memory content is verified. If the Flash is not fully enabled (for example because some configuration registers are not set), you are getting an verification error, even despite the fact the the Flash is correctly programmed.
There are two solutions:
// A.20..23 on P2.4..7 // (Alternate Push-Pull Outputs + enable CS.0/1 P2.0..1) _WDWORD(0xE0005000, (_RDWORD(0xE0005000) | 0x00F3) ); // PC0 _WDWORD(0xE0005004, (_RDWORD(0xE0005004) | 0x00F3) ); // PC1 _WDWORD(0xE0005008, (_RDWORD(0xE0005008) | 0x00F3) ); // PC2 // if necessary other settings that enable external memory // ... LOAD file.ELF INCREMENTAL // load application g, main // run til main (optional)
Article last edited on: 2007-01-28 19:21:31
Did you find this article helpful? Yes No
How can we improve this article?