lpc link2 with hitex 4350 - lpc link2 broken?

[haukekrüger]

Hi everyone,

I have been using a Hitex 4350 board with an lpc link2 debugger for a while now.

This morning, I have noticed that I am no longer able to debug my code. On Sunday, it still worked and there was no code modification afterwards. The failure outputs the following error message:

Debug protocol: JTAG. RTCK: Disabled. Vector catch: Disabled.
inspected v.2 External Flash Device on SPI W:\nxp\LPCXpresso_8.2.2_650\lpcxpresso\bin\Flash\LPC18_43_SPIFI_4MB_64KB.cfx
image 'LPC18/43 Generic SPIFI Jun 21 2016 11:54:07'
Opening flash driver W:\nxp\LPCXpresso_8.2.2_650\lpcxpresso\bin\Flash\LPC18_43_SPIFI_4MB_64KB.cfx
AFTER driver startup timeout
Driver Addresses
Start:  10000000
Entry:  10000035
End:    10001F98
Stack:  10081000
Mailbox:10089000
Driver Register State
R0:     10000F49
R1:     00000001
R2:     00000001
R3:     600F03E8
R4:     40086000
R5:     0ABA9500
R6:     00000000
R7:     00000000
R8:     00000000
R9:     00000000
R10:    00000000
R11:    00000000
R12:    00000000
SP:     10080FC8
LR:     FFFFFFF9 (exception from main thread)
PC:     FFFFFFFE
xPSR:   61000003
MSP:    10080FC8
PSP:    10081000
CFBP:   00000001
Stacked Exception information
10080FE4:  xPSR:   61000000
10080FE0:  VECTPC: 10000F48
10080FDC:  LR:     1000044D
10080FD8:  R12:    00000000
10080FD4:  R3:     600F03E8
10080FD0:  R2:     00000001
10080FCC:  R1:     00000001
10080FC8:  R0:     10000F49
Exception registers
E000ED04:  ICSR:   00400803 (ISRPEND, VECTPEND=0(none), RETTOBASE, VECTACTIVE=3(hard fault))
E000ED28:  MMFSR:  01 (IACCVIOL)
E000ED29:  BFSR:   00
E000ED2A:  UFSR:   0001 (UNDEFINSTR)
E000ED2C:  HFSR:   40000002 (FORCED, VECTBL)
E000ED30:  DFSR:   00000000
E000ED3C:  AFSR:   00000000
E000ED24:  SHCSR:  00000000
E000ED34:  MMAR:   E000EDF8
E000ED38:  BFAR:   E000EDF8
VECTPC instructions near 10000F48
10000F44:  FFFF
10000F46:  FFFF
10000F48:  FFFF
10000F4A:  FFFF
10000F4C:  FFFF
10000F4E:  FFFF
Flash Driver V.2 startup failed - rc Ef(34): Timed-out initializing flash.
NXP: LPC4350  Part ID: 0x00000000
Connected: was_reset=true. was_stopped=false

I found that this problem may be related to the lpc link2 being somewhat in a bad state. I therefore also ran the following command:

lpccript queryflash

The out put is:

Error opening COM5: Read Timeout
Error: <Command line>:0: Read Timeout
   Script cmd:      batchmode 1
   Last target cmd: =print 25888
Terminated with errors

Is there any explanation for this behavior or is that lpc link2 just broken?

Thank you and best regards

Hauke

[haukekrüger]

Hi Carlos,

thank you for your response.

We have investigated on the problem more in detail and tried with various PCs (2xWIn10 + 1xLinux) plus 2 lpcLinkII and a bunch of USB Hubs: the problem with the flash arises sometimes and sometimes it does not. There is no specific setting that causes it - it happens with each of the 2 lpclinkII and on WIndows as well as on Linux. It seems to be a good idea to switch from JTAG debugging to SWD debugging from time to time. It could as well be caused by the Hitex board.

I think that there might be a bug in the toolchain somewhere.

The status is that I can start my code approximately every second attempt - every other attempt, the flash error happens. It is annoying but I can work with it now.

Thank you and best regards

Hauke

[Carlos_Mendoza]

Hi Hauke,

You could try booting the probe manually to make sure it is not what is causing the issue:

Booting LPC-Link2 

Here is a document that gives some information on how to regain debug access to the MCU:

https://community.nxp.com/message/630748 

Hope it helps!

Best Regards,
Carlos Mendoza
Technical Support Engineer