What differences LPC-LINK1 and LPC-LINK2

lpcware · ‎06-15-2016

Content originally posted in LPCWare by fumio yoshizawa on Mon May 16 01:55:45 MST 2016
Hi everyone.

I make custom board on LPC1769.
It is OK connect to debugger LPC-LINK1. But I can't to connect change to LPC-LINK2.
Always error like this.

Failed on connect: Ee(36). Could not connect to core.
No connection to emulator device

Of course delete all *.*launch files in the project workspace.
I wander what cause of error appear.
Regards,
Fumio.

lpcware · ‎06-18-2016

bump

lpcware · ‎06-15-2016

Content originally posted in LPCWare by fumio yoshizawa on Sun May 22 23:21:12 MST 2016
Thank's so much R2D2.
I want to lean more.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by R2D2 on Wed May 18 01:55:34 MST 2016

Quote: fumio yoshizawa
I have a question. Is the simple 4-wire SWD connection need to RESET signal?
I didn't still connect RESET signal. But look like work well.

Yes and No :D

We are using this 'Simple 4-wire SWD' since 2009 for several Cortex-families. Over the years the behavior of LPCXpresso Debugging changed, so that Reset obviously isn't used for all families (at the moment). Nevertheless, long time ago we decided to implement a Standard connector for all our boards and so we always connect Reset, too...

Quote: fumio yoshizawa
"After several tests we decided to add R38 (1k / 402)."
Please tell us more detail. Where to add register? Pull-up?

LPC-link2 schematic:

https://www.embeddedartists.com/sites/default/files/support/xpr/link2/LPC-Link-II_Rev_C.pdf

is showing that an additional R38 can be used to power the buffers (U4,U6,U7) if there's no JTAG-Vref connected or JP2 closed.

[img=1328x747]https://www.lpcware.com/system/files/R38.jpg[/img]

lpcware · ‎06-15-2016

Content originally posted in LPCWare by fumio yoshizawa on Tue May 17 17:57:55 MST 2016
Thank's all, Thank you R2D2,

It's working well use to LPC-Link2. Sorry always mistake to say J1 is open.
This time J1 and J2 are short LPC-Link2 board, And try to debug is going well. I am not understand about VTref.
I have a question. Is the simple 4-wire SWD connection need to RESET signal?
I didn't still connect RESET signal. But look like work well.

"After several tests we decided to add R38 (1k / 402)."
Please tell us more detail. Where to add register? Pull-up?

Regards,
Fumio.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by R2D2 on Tue May 17 01:21:19 MST 2016

Quote: vtw.433e
Suggest you read how to design your debug circuit
https://www.lpcware.com/content/faq/lpcxpresso/debug-design

If you follow this all debug probes will work.

Unfortunately this description isn't very clear :O :((

Quote:
On the LPC-Link2, when JP2 is shunted this will power the target side of the dual-supply buffer and provide power to the target through a diode on VTref. [color=#f00]With JP2 open the target must supply the VTref to power the target side of the dual-supply buffer[/color].

Fumio, if you don't connect VTref you have to close JP2 to power a buffer ;-)

Or you add a resistor as described here:

https://www.lpcware.com/content/forum/minimal-swd-connection-lpc-link2

There's also a description of the usual minimal SWD connection with SWDIO, SWDCLK, Reset and GND :)

If that's not working it could be useful to post your schematic to check Reset- and ISP- pull-ups...

lpcware · ‎06-15-2016

Content originally posted in LPCWare by vtw.433e on Tue May 17 00:40:00 MST 2016
Suggest you read how to design your debug circuit
https://www.lpcware.com/content/faq/lpcxpresso/debug-design

If you follow this all debug probes will work.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by fumio yoshizawa on Mon May 16 22:43:18 MST 2016
Thank you kind replay,

I check LPC-Link2 VCOM driver version. It was ver 2.0.0.0.
I check connection debug signal. I took mistake SWDIO and SWCLK signal.It's opposite way.
Then I connect again.
LPC-Link2 only connect target GND, SWDIO, SWCLK. LPC-ink2 board jumper J1 , J2 are
open. So I think not necessary connect VCC.
But this time appear different err as follow.

Target error from Register access: Ee(FF). Redlink interface error 255.

Regars,
Fumio,

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Mon May 16 08:10:17 MST 2016
The question really becomes:

- is there a problem with your board design? - please reference:

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

- is there a problem with your debug environment/connection when using LPC-Link2

can you attempt a debug connection to another board using the LPC-Link2 probe?

Yours,

LPCXpresso-support

lpcware · ‎06-15-2016

Content originally posted in LPCWare by R2D2 on Mon May 16 02:00:06 MST 2016
Did you read this FAQ :quest:

https://www.lpcware.com/content/faq/lpcxpresso/lpc-link2-failing-enumerate-cmsis-dap-firmware