LPC-Link - Device’s firmware is corrupt error

[lpcware]

Content originally posted in LPCWare by trryt on Fri Apr 02 12:10:21 MST 2010
Yesterday I received my LPCXpresso. Earlier I've read it comes  with blinky demo flashed, but mine wasn't blinking after plugging, but  maybe mine wasn't flashed. But then it went only worse. After installing  the software the only USB device I get in Device Manager is Device with  DFU Capabilities. When I try to debug some demo the software stops at  launching lpc-link. Windows does not detect any hardware changes. In the  log I have error massage "Device’s firmware is corrupt". I have been  searching for some solution, but only found something about running  lpc-link under VM, but I'm using "normal" Windows XP with SP3. I have  tried two USB cables (which work good with other devices), also another  PC. Every-time it's exactly the same. All voltages on LPCXpresso in test  points are OK. Is it by any chance possible that I've downloaded  software version with really corrupt firmware? I assume that this is  LPCXpressoWIN.enc file. Or is it some communication problem? I wanted to  ask this question on NXP forum/knowledge base, but I can't register  there, I don't get the captcha image, only "This reCAPTCHA key isn't  authorized for the given domain" text.
Below is my lpc-link log:
*****************************************************
*** DFU LOG FILE ***
Creation Time :  C:\DOCUME~1\Pawel\LOCALS~1\Temp\dfuApp2305106221789457202.log
*****************************************************
Open Device
Get Device Descriptor successful
Get Configuration Descriptor successful
DFU Get Status successful
---> DFUStatus:
---> DFUState: Device has programmed its memories and is waiting for a  USB reset or a power on reset. (Devices that must enter this state  clear bitManifestationTolerant to 0.)
DFU Abort successful
DFU Get Status successful
---> DFUStatus: Device stalled an unexpected request.
---> DFUState: An error has occurred. Awaiting the DFU_CLRSTATUS  request.
DFU Get State successful
---> DFUState: An error has occurred. Awaiting the DFU_CLRSTATUS  request.
DFU Get Status successful
---> DFUStatus: Device stalled an unexpected request.
---> DFUState: An error has occurred. Awaiting the DFU_CLRSTATUS  request.
DFU Clear Status successful
DFU Get State successful
---> DFUState: Device is operating in the DFU mode and is waiting for  requests.
Download Block Nb 0 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the  host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting  DFU_DNLOAD requests.
Download Block Nb 1 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the  host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting  DFU_DNLOAD requests.
Download Block Nb 2 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the  host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting  DFU_DNLOAD requests.
Download Block Nb 3 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the  host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting  DFU_DNLOAD requests.
Download Block Nb 4 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the  host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting  DFU_DNLOAD requests.
Download Block Nb 5 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the  host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting  DFU_DNLOAD requests.
Download Block Nb 6 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the  host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting  DFU_DNLOAD requests.
Download Block Nb 7 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the  host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting  DFU_DNLOAD requests.
Download Block Nb 8 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the  host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting  DFU_DNLOAD requests.
Download Block Nb 9 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the  host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting  DFU_DNLOAD requests.
Download Block Nb 10 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the  host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting  DFU_DNLOAD requests.
Download Block Nb 11 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the  host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting  DFU_DNLOAD requests.
Download Block Nb 12 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the  host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting  DFU_DNLOAD requests.
Download Block Nb 13 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the  host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting  DFU_DNLOAD requests.
Download Block Nb 14 (1032 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the  host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting  DFU_DNLOAD requests.
Download Block Nb 15 (0 Bytes)
DFU Get State successful
---> DFUState: Device has received the final block of firmware from  the host and is waiting for receipt of DFU_GETSTATUS to begin the  Manifestation phase; or device has completed the Manifestation phase and  is waiting for receipt of DFU_GETSTATUS. (Devices that can enter this  state after the Manifestation phase set bmAttributes bit  bitManifestationTolerant to 1.)
DFU Get Status successful
---> DFUStatus: Device’s firmware is corrupt. It cannot return to  run-time (non-DFU) operations.
---> DFUState: Device has programmed its memories and is waiting for a  USB reset or a power on reset. (Devices that must enter this state  clear bitManifestationTolerant to 0.)
Close Device
  *** END OF FILE ***

[lpcware]

Content originally posted in LPCWare by Rob65 on Wed Dec 07 09:53:37 MST 2011
It might be a good idea to read datasheets and look at the schematics before attaching stuff to your board.

The lpc1227 is a controller with 3.3V power supply, not 5V and the I/O pins are 3.3V tolerant and [B][COLOR=Red]not 5V tolerant as with e.g. the lpc1343[/COLOR][/B] !!!

Attaching anything to your LPCXpresso board without understanding the datasheet may damage your device. Please don't blame us when you are branded with an NXP logo on your finger when touching your chip to see if it's getting hot :eek:

Rob

[lpcware]

Content originally posted in LPCWare by Chaoyin on Wed Dec 07 09:37:11 MST 2011

---

Quote: Zero
I suspect connecting your external device wasn't a good idea :rolleyes:

Did you try to supply and measure VIF current before? Is you device really expecting  3.3V or is it a 5V chip?

If you download schematic of LPCXpresso you can find there diode D6 (page 4), which is used to protect your target board.
Could be a good idea to check this diode :)

---

Thank you for your replay.
Why do you think it is not a good idea to connect a external device? I would like to utilize lpc board to control my external device through the spi interface

My device is a 5V chip. Is the lpc1227 board not supported for the 5V Chip?

[lpcware]

Content originally posted in LPCWare by Ex-Zero on Wed Dec 07 09:19:17 MST 2011
If your LPCXpresso is self powered (=USB connected) this is 3.3V Output.

If not (no USB connected) there's of course no 3.3V Output, then you have to supply your target board with 3.3V.

[lpcware]

Content originally posted in LPCWare by Chaoyin on Wed Dec 07 09:11:20 MST 2011
could anyone kindly tell what it means

J6-28)-------VIO_3V3X -> VOUT(+3.3V out) if self powered, else +3.3V input

the Quell: LPCXpressoLPC1200revB.pdf

Thanks

[lpcware]

Content originally posted in LPCWare by Ex-Zero on Wed Dec 07 09:08:58 MST 2011

---

Quote:
  Could anyone explain how it happens and how to solve it?

---

I suspect connecting your external device wasn't a good idea :rolleyes:

Did you try to supply and measure VIF current before? Is you device really expecting  3.3V or is it a 5V chip?

If you download schematic of LPCXpresso you can find there diode D6 (page 4), which is used to protect your target board.
Could be a good idea to check this diode :)

[lpcware]

Content originally posted in LPCWare by Chaoyin on Wed Dec 07 07:47:11 MST 2011
Hallo everybody,

i am a user of lpc1227. For my project i am trying to use the SPI interface of lpc 1227 (master) to communicate with a peripheral ATA5279 (slave). At the side of the slave it need the input digital supply voltage which comes from the microcontroller of the master. As i connect the hardware of master and slave with the following writing description:

Master (lpc1227)  ------->       Slave(ATA5279)
3.3V (J6-28)  ---> VIF
SSEL(PIO0_15) ---> S_CS
GND --->  GND
MOSI(PIO0_17) ---> MOSI
MISO(PIO0_16) ---> MISO
SCLK(PIO0_14) --> S_CLK

the LED2 of the LPC1227 lights not any more. I have tried to find out what has happened with my lpc board. A short circuit between the VIF and GND was occurred. This leads to the broken of my second lpc board:mad::mad::mad:. Has anyone the same unpleasant experience?  Could anyone explain how it happens and how to solve it?

Any advices/suggestions are appreciated.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Fri Jul 30 00:11:32 MST 2010
This is actually a fault with your board. Please ask your supplier for a replacement board.

[lpcware]

Content originally posted in LPCWare by gus053 on Thu Jul 29 12:27:04 MST 2010
Hi all. Sorry to reopen the thread but I have a similar problem; the user led blinks, the windows recognize the hardware and the example compiles well in the IDE, but when I try to write the program in the chip, the computer waits and waits, and never connect with the hardware, and in the logs says something about corrupted firmware (I attach the log file). I'm not able to program it. To whom I need to ask for a new board? I bought it from FARNELL, but I don't know if I need to talk with them or directly with NXP. In that case, who is the contact person?

Thanks a lot for your help.

[lpcware]

Content originally posted in LPCWare by trryt on Sat May 01 09:58:42 MST 2010
I got replacement board from NXP and EA support told me that the cause of the problem was that the board left factory with fuses unprogrammed. So I consider this thread closed.

[lpcware]

Content originally posted in LPCWare by trryt on Sun Apr 04 07:37:30 MST 2010
I really wanted to check what's up with this board and I reconfigured LP3154 for UART booting. It reacted as I supposed: PC no longer detects it, and after 1 minute of waiting the LED1 stars to blink and blinks for two minutes. So I tried to send some image to it, as the RXD pin is available on the board. First I compiled some program with Keil and tried to convert it using lpc313xImgCreator.exe, but the board always start to blink directly after sending the image. I'm not sure about methods of converting the bin file to the image good for the bootloader, so maybe my image was actually bad. But I've found AN10811, with timer_example_crc.rom which has to be valid image and I get the same effect the board blinks indicating wrong image. So it indicates wrong encrypted image over DFU and wrong unencrypted image over UART, so maybe it was prepared for encrypted images, but with wrong key, not the one for LPC-Link....

[lpcware]

Content originally posted in LPCWare by trryt on Sat Apr 03 13:14:44 MST 2010
I've been reading LPC3154 user manual and as far as I understand it good when LPC3154 doesn't get the right firmware over USB in DFU mode it should change the state of GPIO2, so the LED1 should blink and it's always off. So I'm even more convinced that the board is dead.

[lpcware]

Content originally posted in LPCWare by trryt on Sat Apr 03 08:38:27 MST 2010
OK. Thank you, I'll wait for their reply.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Sat Apr 03 02:50:30 MST 2010
From your description, this does sound like a dead board. I have asked somebody from NXP/EA to contact you.

[lpcware]

Content originally posted in LPCWare by trryt on Sat Apr 03 01:45:22 MST 2010
As you suggested I send a message in the contact box on http://www.lpc1100challenge.com/contactus asking for another board. I can't find another way to contact challenge team.
I can't say either is the board really dead or just never flashed at all. As I wrote in first post all voltage regulators are working and USB interface is working, but for sure I can't use it as it was meant to be used. And for me it is the first time I hear about some kind problem too. I read about programming problems, but they all are different from mine. So I can only assume I am the first contestant who got the board dead straight from factory.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Fri Apr 02 18:51:45 MST 2010
I can't know if the fuses are configured incorrectly, or not at all. The board doesn't work out of the box, and you've never been able to flash it. The real question is whether it works at all? I do not necessarily suggest you send it back. It's possible the LPC Challenge does not need the return. You should simply ask for another. I know it doesn't help, but this is the first time I've heard of a DOA (Dead On Arrival) board. I don't know if Embedded Artists AB (Sweden) can help, but they are in your time zone. It doesn't hurt to ask.

Regards,

CodeRedSupport

---

Quote: trryt
Hi,
Thank you for your quick reply.
I've received my board from Lpc1100challenge and frankly I've no idea how could I ask for replacement and sending it back to US is quite irrational for me as long as I got it for free and postal costs would be bigger than costs of similar boards here in Poland.
So I only can ask what can I do with the board on my own.
From you answer I understand that LPC-link does not have program flash but has some fuse bits (like these in AVR chips) and they are configured wrong. Is it some way to configure them, maybe by using some other JTAG programmer?
Or maybe if my board isn't flashed at all and we can assume that fuse bits are in default state is it possible to get firmware image compatible with this state?
I really got excited about Lpc1100challenge and getting to know new ARMs from NXP and new development environment and I wouldn't like to end up with frustration and disappointment I'm feeling now...

---

[lpcware]

Content originally posted in LPCWare by trryt on Fri Apr 02 15:52:02 MST 2010
Hi,
Thank you for your quick reply.
I've received my board from Lpc1100challenge and frankly I've no idea how could I ask for replacement and sending it back to US is quite irrational for me as long as I got it for free and postal costs would be bigger than costs of similar boards here in Poland.
So I only can ask what can I do with the board on my own.
From you answer I understand that LPC-link does not have program flash but has some fuse bits (like these in AVR chips) and they are configured wrong. Is it some way to configure them, maybe by using some other JTAG programmer?
Or maybe if my board isn't flashed at all and we can assume that fuse bits are in default state is it possible to get firmware image compatible with this state?
I really got excited about Lpc1100challenge and getting to know new ARMs from NXP and new development environment and I wouldn't like to end up with frustration and disappointment I'm feeling now...

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Fri Apr 02 13:35:23 MST 2010
LPCXpressoWIN.enc is an encrypted version of the probe image, which should match the AES encryption your board shipped with. The DFU utility complains your firmware is corrupt. Unless the fuse configuration on your LPCXpresso is a match for the image, the DFU can't succeed. Given the fact your LPCXpresso board also does not appear to have the standard blinky demo installed in flash, you should return the board to your vendor for a replacement.

Regards,

CodeRedSupport