ULINK: MEMORY MISMATCH AT DEBUGGER START
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:
The following Discussion Forum threads may provide information related to this topic.
Last Reviewed: Thursday, September 24, 2015
of your data.