LPC MicrocontrollersのトピックRe: j-lite cant identify LPC1788 and talk to it

j-lite cant identify LPC1788 and talk to it

lpcware — Wed, 15 Jun 2016 17:57:22 GMT

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

Re: j-lite cant identify LPC1788 and talk to it

lpcware — Wed, 15 Jun 2016 17:57:23 GMT

Content originally posted in LPCWare by usb10185 on Thu Feb 23 09:53:38 MST 2012
Hi,
A few suggestions.
You can use Flashmagic to check and clear the CRP level if it is lower than CRP3.
Try the JLINK with another target to ensure it is working.

Re: j-lite cant identify LPC1788 and talk to it

lpcware — Wed, 15 Jun 2016 17:57:24 GMT

Content originally posted in LPCWare by Haldor on Thu Aug 16 09:17:52 MST 2012
I have used the FDI uEZGUI-1788-43WQS kit successfully.

The problem is with the J-Link Lite LPC edition debugger. It works fine with ARM7 NXP processors, but it is too slow to debug Cortex M3 processors. You can use the LPC edition to download programs to the LPC1788, but even that is not a sure thing. Depending on what I am doing with the LPC1788 I have had problems that required me to disconnect the J-Link Lite LPC debugger from the development board after downloading and then power the development board down and back up before the program started running properly. A bit of a pain, but hey, we all really prefer to debug with printf statements, right?

P.S. I have never had a Cortex M3 board damaged by the J-Link Lite LPC edition, it simply doesn't support debugging with them.

I just bought a Segger J-Link (the $300 version) and found out that the J-Link Lite LPC edition also used a non-standard JTAG cable (probably because it was designed before the 9 Pin Cortex M3 standard). I purchased the Cortex M3 9 pin adapter from Seggar only to find out that while it is pinned out the same as the J-Link Lite LPC edition, it uses a 2mm connector instead of the 0.05" connector used by the Cortex M3 9 pin connector. Argg.

I am looking to see if NXP or FDI has an adapter cable, but if they don't then I will need to fabricate my own. I do wish Segger would offer that adapter since they are still selling the J-Link Lite LPC debugger.

Does anyone know if there is a commercially available adapter to go from the standard 20 pin 0.1" JTAG to the 10 pin 2mm connector used by the J-link Lite LPC edition?

Re: j-lite cant identify LPC1788 and talk to it

lpcware — Wed, 15 Jun 2016 17:57:25 GMT

Content originally posted in LPCWare by Haldor on Thu Aug 16 09:24:05 MST 2012
Answered my own question. FDI has the 20 pin J-Tag to 2mm 10 Pin adapter and you can order it from Digikey.

http://www.digikey.com/product-detail/en/JLINK-ARM-AD/622-1039-ND/2631978

Re: j-lite cant identify LPC1788 and talk to it

lpcware — Wed, 15 Jun 2016 17:57:26 GMT

Content originally posted in LPCWare by yuho on Tue Aug 28 04:58:26 MST 2012
I have same problem.
I solved the problem by using FlashMagikTооl. Erasing the chip and it works.