• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 20 subscribers
  • Views 1111 views
  • Users 0 members are here
Options
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

uvopt file corrupt after debug session

Stephen Isidore

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

0