Content originally posted in LPCWare by Prolepsis on Wed Oct 16 15:35:09 MST 2013
Hi all,
I'm using the LPCxpresso board to investigate the LPC1769 as a potential embedded platform upgrade for my company. During my investigations, I started having problems with the USB connection (occasionally requiring a disconnect/reconnect of the board) up until today when the thing just all-out died and reported the following error:
[color=#00c]LPCXpresso Debug Driver v5.2 (Jul 5 2013 11:31:15 - crt_emu_cm3_nxp build 15)
Looked for chip XML file in C:/nxp/LPCXpresso_5.2.6_2137/lpcxpresso/bin/LPC1769.xml
Looked for vendor directory XML file in C:/nxp/LPCXpresso_5.2.6_2137/lpcxpresso/bin/nxp_directory.xml
Found generic directory XML file in C:/nxp/LPCXpresso_5.2.6_2137/lpcxpresso/bin/crt_directory.xml
Emu(0): Conn&Reset. DpID: 2BA01477. Info: HID64HS12
SWD Frequency: 3000 KHz. RTCK: False. Vector catch: False.
Packet delay: 0 Poll delay: 0.
Loaded LPC175x_6x_512.cfx: LPC175x_6x (512K) Apr 22 2013 12:14:31 On-chip Flash Memory
NXP: LPC1769 Part ID: 0x00000000
Connected: was_reset=false. was_stopped=true
v Registered license, download limit of 128K
[color=#f00]Flash driver "Init" timeout (1500 ms) PC: FFFF2C0C
Flash driver "UnInit" return code: 0x0
15: Target error from Commit Flash write: Ef(34). Timed-out initializing flash.[/color]
Stopped: Halt[/color]
I'm still poking around, but I'm suspecting that something browned out during flash write (one of the issues it reported was excessive power consumption), got corrupted and overwrote the flash driver tucked away in the device. Is this a likely failure path? If so, how would I go about reimaging the device? I'm half leaning on just ditching the LPC Link and falling back to a dedicated powersupply + 3rd party JTAG.
Am I on the right path or barking up the wrong tree?
Thanks!
