lpc11c24 dead ?

[lpcware]

Content originally posted in LPCWare by hetii on Tue Jun 10 12:17:48 MST 2014
Hi

I order two lpcxpresso board with lpc11c24 as a target MCU.

On the first I did:

dfu-util -d 0x471:0xdf55 -c 0 -t 2048 -R -D /usr/local/lpcxpresso_7.2.0_153/lpcxpresso/bin/LPCXpressoWIN.enc
dfu-util 0.5

(C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc.
(C) 2010-2011 Tormod Volden (DfuSe support)
This program is Free Software and has ABSOLUTELY NO WARRANTY

dfu-util does currently only support DFU version 1.0

Filter on vendor = 0x0471 product = 0xdf55
Opening DFU USB device... ID 0471:df55
Deducing device DFU version from functional descriptor length
Run-time device DFU version 0100
Claiming USB DFU Runtime Interface...
Determining device status: state = dfuIDLE, status = 0
WARNING: Runtime device already in DFU state ?!?
Found Runtime: [0471:df55] devnum=0, cfg=1, intf=0, alt=0, name="UNDEFINED"
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Deducing device DFU version from functional descriptor length
DFU mode device DFU version 0100
No valid DFU suffix signature
Warning: File has no DFU suffix
bytes_per_hash=583
Copying data from PC to DFU device
Starting download: [##################################################] finished!
state(8) = dfuMANIFEST-WAIT-RESET, status(0) = No error condition is present
Done!
can't detach
Resetting USB to switch back to runtime mode

#Now time to flash:

$ /usr/local/lpcxpresso_7.2.0_153/lpcxpresso/bin/crt_emu_lpc11_13_nxp -wire=winusb -pLPC11C24/301 -flash-load-exec=nxp_lpcxpresso_11c24_freertos_blinky.axf
Ni: LPCXpresso Debug Driver v7.2 (May 13 2014 18:29:32 - crt_emu_lpc11_13_nxp build 1263)
Xs:
Xc:
Nc: Emu(0): Conn&Reset. DpID:  BB11477. Info: LPCLINK_1_1
Nc: SWD Frequency: 3000 KHz. RTCK: False. Vector catch: False.
Nc: Packet delay: 0  Poll delay: 0.
Nc: Loaded LPC11_12_13_32K_8K.cfx: LPC11_12_13 (32K Flash, min 8K RAM) Apr 22 2013 12:14:02  On-chip Flash Memory

Nc: NXP: LPC11C24/301  Part ID: 0x00000000
Cr:v LPCXpresso Free License - Download limit is 256K
Nt: Loading ELF file 'nxp_lpcxpresso_11c24_freertos_blinky.axf' at location 00000000
Xs:
Nc: nSRST assert (if available)
Nc: Executing in user flash.

All fine, LED blink.

On the second I did the same:

dfu-util -d 0x471:0xdf55 -c 0 -t 2048 -R -D /usr/local/lpcxpresso_7.2.0_153/lpcxpresso/bin/LPCXpressoWIN.enc
dfu-util 0.5                                                                                                                                                              
                                                                                                                                                                          
(C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc.                                                                                                           
(C) 2010-2011 Tormod Volden (DfuSe support)                                                                                                                               
This program is Free Software and has ABSOLUTELY NO WARRANTY                                                                                                              
                                                                                                                                                                          
dfu-util does currently only support DFU version 1.0                                                                                                                      
                                                                                                                                                                          
Filter on vendor = 0x0471 product = 0xdf55                                                                                                                                
Opening DFU USB device... ID 0471:df55                                                                                                                                    
Deducing device DFU version from functional descriptor length                                                                                                             
Run-time device DFU version 0100                                                                                                                                          
Claiming USB DFU Runtime Interface...                                                                                                                                     
Determining device status: state = dfuIDLE, status = 0                                                                                                                    
WARNING: Runtime device already in DFU state ?!?                                                                                                                          
Found Runtime: [0471:df55] devnum=0, cfg=1, intf=0, alt=0, name="UNDEFINED"                                                                                               
Claiming USB DFU Interface...                                                                                                                                             
Setting Alternate Setting #0 ...                                                                                                                                          
Determining device status: state = dfuIDLE, status = 0                                                                                                                    
dfuIDLE, continuing                                                                                                                                                       
Deducing device DFU version from functional descriptor length                                                                                                             
DFU mode device DFU version 0100
No valid DFU suffix signature
Warning: File has no DFU suffix
bytes_per_hash=583
Copying data from PC to DFU device
Starting download: [##################################################] finished!
state(8) = dfuMANIFEST-WAIT-RESET, status(0) = No error condition is present
Done!
can't detach
Resetting USB to switch back to runtime mode

#time to flash:

$ /usr/local/lpcxpresso_7.2.0_153/lpcxpresso/bin/crt_emu_lpc11_13_nxp -wire=winusb -pLPC11C24/301 -flash-load-exec=nxp_lpcxpresso_11c24_freertos_blinky.axf
Ni: LPCXpresso Debug Driver v7.2 (May 13 2014 18:29:32 - crt_emu_lpc11_13_nxp build 1263) <= Here it freeze.

As we can see on the second board flash utility freeze.
The led shine all the time.

Is my target mcu dead? What can i do more to test it?

Update 1: I just replace lpc11c24 from this board and still had the same issue

Update 2: I dissolder pad beetwen lpclink and target board and use LPClink from working board to flash target boarad that have my issue.
                This step success, so something is wrong with LPClink on my non working board.
                As I notice, the LED1 start blinking and after a while stop.
                Current traceback looks like that:

/usr/local/lpcxpresso_7.2.0_153/lpcxpresso/bin/crt_emu_lpc11_13_nxp -wire=winusb -pLPC11C24/301 -flash-load-exec=nxp_lpcxpresso_11c24_freertos_blinky.axf
Ni: LPCXpresso Debug Driver v7.2 (May 13 2014 18:29:32 - crt_emu_lpc11_13_nxp build 1263)
Nc: Emu(0): Conn&Reset. DpID:  BB11477. Info: LPCLINK_1_1
Nc: SWD Frequency: 3000 KHz. RTCK: False. Vector catch: False.
Nc: Packet delay: 0  Poll delay: 0.
Nc: Loaded LPC11_12_13_32K_8K.cfx: LPC11_12_13 (32K Flash, min 8K RAM) Apr 22 2013 12:14:02  On-chip Flash Memory

Nc: NXP: LPC11C24/301  Part ID: 0x00000000
Cr:v LPCXpresso Free License - Download limit is 256K
Nt: Loading ELF file 'nxp_lpcxpresso_11c24_freertos_blinky.axf' at location 00000000 <= freeze here.

Maybe some of the jtag buffer are corrupted

Best Regards.

[lpcware]

Content originally posted in LPCWare by hetii on Fri Jun 13 10:05:05 MST 2014
Hi there :)

Based on your tips I change cables and now my second board works :)

For testing I back to my old cables and now they also works, so maybe there is some issue with my usb ports (its odd cause I try different one).

I will monitor my boards and let you know if cath some other issue :)

Meantime thanx for yours time.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Wed Jun 11 23:46:46 MST 2014
LED1 is controlled by the debug probe firmware, and simply indicates that communication is taking place between the probe and the target.

During one part of production test a demo/test application is downloaded via the LPC-Link side to the target MCU. So your board worked at that point.

Beyond that, I'm not sure what else to offer here, other than trying a different cable (as suggest by Pacman), and potentially a different USB port - or connecting via a powered USB hub.

You might do best just cutting your loses and getting a new one.

Regards,
LPCXpresso Support

[lpcware]

Content originally posted in LPCWare by Pacman on Wed Jun 11 22:13:47 MST 2014
First of all, I've never used LPCExpresso, so I might be completely off in parts of this reply!

Make sure you're not using two different USB cables. :)
Why ?
-Once I had a problem with two identical boards. One would work, another wouldn't.
I used two different USB cables, and since USB cables are usually manufactured by low-cost wires (the lowest possible), the resistance in the cables might be too high for the voltage to reach the target.
I've measured some (bad) cables to be more than 2 Ohms on 0.6 meter (2 ft), and some (good) cables to be less than 0.5 Ohm on 1.8 meter (6 ft).

So try plugging it into the same cable.

If you're already using the same cable, and the results differ, the problem could be in your firmware.
If a variable is not initialized correctly, it will most likely cause periodic errors.

I'm believing, that in this case it's a firmware bug. I believe an interrupt crashes the chip, preventing it from running.
If the LED starts blinking and stops after a while, it indicates that the firmware was running, but crashed. Yes, the crash can be because of lack of power (monitor your voltage supply and your current usage).

Have you tried running the program without using the debugger ?

Other than the above mentioned, nothing comes to mind what could be wrong; but it's worth checking out. Make sure you check the voltage that the chip receives.

[lpcware]

Content originally posted in LPCWare by hetii on Wed Jun 11 03:05:38 MST 2014
Hi again.

I provide external power supply to +5vin or directly to usb port, and have still the same issue.

For testing I try flash two application, the nxp_lpcxpresso_11c24_periph_blinky.axf and nxp_lpcxpresso_11c24_freertos_blinky.axf, cause they blink in different way.

As I observe the flashing process start (LED 1 start blinking, but not always) after a while process hangs.

Then sometimes when I replug my board to power, the LED2 start blinking, so it means that it was flashed correctly.

Maybe indeed there is an issue with power line.

Any tips what can i check next?

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Wed Jun 11 01:02:32 MST 2014
Unfortunately your description doesn't sound like any other LPCXpresso board problem report I can ever recall seeing previously.

From the latest log that you provided, it would appear that the LPC-Link firmware had been downloaded correctly to the debug probe, and then when you ran the crt_emu debug utility, this was managing to communicate to the target MCU over the SWD connection, as it has managed to read the ID Code of the Cortex-M0 inside the LPC11C24 MCU.

The only thing I can think of to check would be power being supplied. As it appears to be freezing at the start of programming flash, and this consumes considerably more power than just starting a connection.  The power supplied by USB ports can be a bit variable, so try a different USB port, or better still connect via a powered USB hub.

I'm not sure what else I can suggest here, particularly now that you have made multiple hardware modifications to your 'problem' board.

Regards,
LPCXpresso Support