I'm working with a board based on LPC3250 chip and my uvopt file is always bad after debugging session.
I've found the following line in uvopt file :
<TargetDriverDllRegistry> <SetRegEntry> <Number>0</Number> <Key>DLGTARM</Key> <Name>Hõ</Name> </SetRegEntry> <SetRegEntry> <Number>0</Number> <Key>ARMDBGFLAGS</Key> <Name></Name> </SetRegEntry> <SetRegEntry> <Number>0</Number> <Key>UL2ARM</Key> <Name>-UV0335AAE -O14 -S0 -C1 -N00("Unknown JTAG device") -D00(1B900F0F) -L00(4) -N01("ARM926EJ-S Core") -D01(17900F0F) -L01(4) -FO11 -FD8000000 -FC800 -FN1 -FF0LPC32x0_M29W320ET_ERAM -FS080010000 -FL0400000</Name> </SetRegEntry> </TargetDriverDllRegistry>
the corrupt line is : <Name>Hõ</Name>
after debug i'm lossing "programming algorithm"
Somebody have an idea
thanks
"<Name>Hõ</Name>""
I remember seeing something very similar a few years ago when updating a project from uVision version 3 to 4.
I mentioned it to Keil support, who sent me an updated uVision 4. At the time, this was a pre-release.
Since upgrading those projects (with their update), I've not seen it since.
If you've got an older copy of uVision 4, then you should probably update. Otherwise, I suggest you ask Keil support.
Could that be something to do with your language setting in Windows...?
Note
I'm also working onto target based on LPC2000 with the same environment (PC and IDE) and I've no problem