lpcware

j-lite cant identify LPC1788 and talk to it

Discussion created by lpcware Employee on Jun 15, 2016
Latest reply on Jun 15, 2016 by lpcware
Content originally posted in LPCWare by siriasis on Tue Jan 24 16:39:17 MST 2012
Hi Guys. We have recently purchased two kits: uEZGUI-1788-43WQS from FDI one after another and they both stopped working after a few debug sessions with Crossworks IDE.
The JTAG(segger j-lite) that is included in the kit can’t talk anymore to NXP chips on these boards. Below is the screen shot of the J-link commander output.  I don’t know what could cause the problem.

SEGGER J-Link Commander V4.41e ('?' for help) Compiled Jan 19 2012 16:21:49 DLL version V4.41e, compiled Jan 19 2012 16:21:29
Firmware: J-Link ARM Lite V8 compiled Jan 12 2012 20:49:19
Hardware: V8.00
S/N: 228002481
VTarget = 3.313V
Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000 No devices found on JTAG chain. Trying to find device on SWD.
No device found on SWD.
Did not find any core.
Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000 No devices found on JTAG chain. Trying to find device on SWD.
No device found on SWD.
Did not find any core.
J-Link>


I checked the JTAG pins: they are all fine. even something is present on a TDO(data from the CPU) line when the connection is being established.

At first, when the first kit was killed we thought about static. But when the second board was killed while I was wearing an antistatic strap we started to have some doubts that it happens due to a static.

I have also noticed that the second time it stopped working when I plugged the USB cable to the on-board USB connector. The board is powered from this connector. We checked the suppressor U6 connections(may be 5 volt intput on a USB  was not properly suppressed) but they were normal. 
We are now making a flash programmer to check whether the cpu is dead or alive. We are going to perform a whole erase with the help of flash magic tool and a programmer. Perhaps the CPU was locked somehow(CRP1 bit is set). This is also a mystery what could cause the CPU to lock. What do you think about it?


Guy did anyone work with these kits before. Did you have the same problems. Do you know what can cause it?


Thank you for your help

Outcomes