LPC-LINK problem (XML Error in directory file nxp_lpc17xx.xme on line 196:)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

LPC-LINK problem (XML Error in directory file nxp_lpc17xx.xme on line 196:)

264 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by pig_man on Mon Sep 20 09:40:18 MST 2010
I tried to boot my board with LPC1767 with the source code (LPCXpresso1768_systick_twinkle) from the LPC1768 reference board (with the processor setting changed to LPC1767) .  I kept getting this message:

LPCXpresso Debug Driver v2.0 (Aug 31 2010 23:37:18)
Looked for chip XML file in D:/nxp/lpcxpresso_3.5/bin/LPC1767.xml
Looked for vendor directory XML file in D:/nxp/lpcxpresso_3.5/bin/nxp_directory.xml
Found generic directory XML file in D:/nxp/lpcxpresso_3.5/bin/crt_directory.xml
Emu(0): Conn&Reset. DpID: 2BA01477. Info: T1S6RGRIA
SWD Frequency: 3000 KHz. RTCK: False. Vector catch: False.
Packet delay: 0  Poll delay: 0.
XML Error in directory file D:/nxp/lpcxpresso_3.5/bin/nxp_lpc17xx.xme on line 196: Element enclosed in invalid element nesting: 'peripheralInstance'.
03: Failed on chip setup: Ec(01). Invalid, mismatched, or unknown part

I verified the Part ID is 0x26012837, so the LPC-link is talking to the device correctly.  However, I can't get any further.  Do I have to use LPC1768 with LPC-link?  Did I miss something else?

Thank you.
0 Kudos
2 Replies

245 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Mon Sep 20 10:03:39 MST 2010

Quote: CodeRedSupport
This is fixed in the next version of LPCXpresso after v3.5.0


In the meantime, you can use the attached to patch LPCXpresso 3.5.0. This will allow connection to LPC1767 (and LPC1763).

Please unzip the attachment and put the file (nxp_lpc17xx.xme) into your  <install>/bin directory, overwriting the existing file with the  same name.

Regards,
CodeRedSupport.
0 Kudos

245 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Mon Sep 20 09:47:59 MST 2010
This is fixed in the next version of LPCXpresso after v3.5.0
0 Kudos