LPC4323: can't debug it with lpc-link

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

LPC4323: can't debug it with lpc-link

562 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by cyba on Fri Feb 06 10:12:54 MST 2015
Hello,
I'm working on a new custom target board with a LPC4323JBD144 micro (a new one nxp sample with blank memory), I'm trying to download a simple basic test program but lpc-link can't connect to the target via JTAG 10pin connection. LpcLink seems to detect 1 available JTAG Device, the target device is reported as: Target Device with TAP id 0x4906002b (see attached figure) but the device can communicate further.
I know that this situation is typical of a new hardware and a new board so I've checked for all the typical mistakes already detailed on lpcware forum.
I've already checked all the jtag pins on micro and verified the right signals, I've already checked the power supply and groud pins and they seems to be ok.
I also tried to program the simple code with flash magic starting with ISP by uart0 but flash magic says "Device signature doesn't match the expected values",  and when I try to program it give me the error message:"invalid value or command sent. Please try the operation again" (but flash erasing procedure, flash memory view, CRC check  seems to be right after the initial message "device signature doesn't match...")
Anybody can help me? Any idea about my problem?
thanks
Labels (1)
0 Kudos
4 Replies

492 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by cyba on Tue Feb 10 03:28:18 MST 2015
Thanks for the support and the infos...
---- SOLVED -----
DBGEN pin killed me too! It must be tied high!
0 Kudos

492 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Sat Feb 07 06:53:03 MST 2015
THE JTAG Tap ID you are reporting in you initial post is definitely not correct for LPC43xx. You should see TAP Id = 0x4ba00477 for the Cortex-M4 and TAP Id = 0x0ba01477, for the Cortex-M0.

I would suggest that you double check you debug/reset circuitry against...

http://www.lpcware.com/content/faq/lpcxpresso/debug-design

Also try booting into ISP mode:

http://www.lpcware.com/content/faq/lpcxpresso/regaining-debug-access

And also make sure you have the debug cable connected from the target to the debug probe the right way around!

You could also try changing your connection from JTAG to SWD. This will mean that you cannot carry out dual core debugging, but might show whether the issue is with one of the pins used for JTAG but not SWD. This can be done via the launch configuration menu:

http://www.lpcware.com/content/faq/lpcxpresso/launch-configuration-menu

You might also find some of the information in the below FAQ useful as background:

http://www.lpcware.com/content/faq/lpcxpresso/lpc43xx-multicore-apps

PS - the fact that you can't get flashmagic to talk to the part over UART would tend to indicate that you have something pretty fundamentally wrong with your board (or that you have somehow blown the MCU).

Regards,
LPCXpresso Support
0 Kudos

492 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by cyba on Sat Feb 07 04:47:56 MST 2015
that's right, sorry!
I use the latest LPCXpresso v7.6.2_326 on win8.1-64b.
Here's the debug log:
LPCXpresso Debug Driver v7.6 (Jan 28 2015 22:21:11 - crt_emu_lpc18_43_nxp build 50)
Failed on connect: Ep(01). Target marked as not debuggable.
Conn&Reset. Was: None. DpID: FFFFFFFE. Info: WIN64HS12

And here attached the a detailed image and the boot log
0 Kudos

492 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Fri Feb 06 10:24:58 MST 2015
You don't menti which version of LPCXpresso you are using. I would suggest making sure you are using the latest. If that doesn't help, post the Debug log.
0 Kudos