I have managed somehow to set my Cortex-M-device in a state where flashing is no more possible ( using uVision4 and ulink2 ).
It is for sure that this has something to do with the last code I have flashed
There are already several postings about this topic in the web, so this is nothing new.
I have tried the known ways like reducing the clock-speed, try different reset-options eg, but all fails.
I faced this problem already but was able to connect later again, but now it looks like matters are much more difficult.
Obviously, the code has direct impact on the "strength" of this issue, there may be a way out or not.
I have read about a solution by adding some delay during startup, but at least for this board this seems to be to late,
therefore a new one is on it's way.
For future versions I will probably use external flash only + delay inside startup-code and switch to internal flash only in case
the code is running.
This avoids booting always from internal flash by automatic on the EVB used, no matter what boot-options are set