LPC_LINK Works, Red Probe+ Does Not

lpcware · ‎06-15-2016

Content originally posted in LPCWare by richas on Wed Nov 16 16:17:45 MST 2011
I am using an LPCxpresso lpc1114 eval board, split in two. I am using the LPCXpresso IDE. Simple blinky project.

Removing all connections between the LPC-LINK and the target board except for SWDIO, SWCLK, Reset, GND, and Vcc works.

Using the same signals with the Red Probe+ fails with two error messages:

The first is a Visual Studio debugger message "unhandled win32 exception occured in crt_emu_lpc11_13_nxp.exe"

The second is an LPCXPRESSO error "error launching Debug/test.axf remote communication error. Target disconnected.:No Error.:"

With regards to the Red Probe+ 20 pin connector I have:

GND to pin 2,4,6,8,10,12,14,16,18, and 20
vcc to pin 1
SWDIO to pin 7
SWCLK to pin 9
reset to pin 15

The power led on the probe+ lights.

Thanks

Rich

lpcware · ‎06-15-2016

Content originally posted in LPCWare by SteveClevenger on Thu Dec 01 17:05:12 MST 2011

Quote: richas
Added pullups, no change. The signals have some ringing so I added 100pF caps which helped. No change though, still no response when let in the default wire speed (none selected).

This testing caused me to notice that when the wire speed is set to the default I don't see any activity on reset, swdio, or swclk. Interesting?

It is working now when set to 30000 so that is good though knowing the cause would be nice.

Rich

By the way, ARM recommends to pull-down (instead of pull-up) TCK only.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by richas on Thu Dec 01 15:06:32 MST 2011
Added pullups, no change. The signals have some ringing so I added 100pF caps which helped. No change though, still no response when let in the default wire speed (none selected).

This testing caused me to notice that when the wire speed is set to the default I don't see any activity on reset, swdio, or swclk. Interesting?

It is working now when set to 30000 so that is good though knowing the cause would be nice.

Rich

lpcware · ‎06-15-2016

Content originally posted in LPCWare by richas on Thu Dec 01 14:41:22 MST 2011
No, no pullups, perhaps that is it........ I will add and report.

Thanks

Rich

lpcware · ‎06-15-2016

Content originally posted in LPCWare by SteveClevenger on Thu Dec 01 14:19:25 MST 2011

Quote: richas
I found it, thank you. This is the kind of thing I HATE. Yesterday I tried slower and slower "wire speeds" and got a different error, related to wire errors...

This morning I tried it and it works! (ugh) Any wire speed setting (even 30000) besides the "empty" default setting works. Setting it back to the empty default repeatedly causes it to fail.

Rich

Wire errors suggest you've got problems with the physical debug connection(s). Red Probe+ attempts to adjust logic levels based on the voltage it sees on Vtref referenced to whatever GND it has to work with. That's why you need a good GND, shared with your target hardware. The voltage at Vtref is coming from your hardware. Do you use pull-ups (typically 10K-100K ohm) on the JTAG/SWD lines?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by richas on Thu Dec 01 10:25:50 MST 2011

Quote: CodeRedSupport
In addition to trying out changing the wire speed as suggested by the previous poster, can you please confirm:

- What actually is your target board? Is it the MCU portion of an LPCXPresso 1114 board that you have split into 2, or is it a board of your own design?

I have tried both my target board and 1/2 (cut in half) of the LPC1114 LPCxpresso board, same results.

Assuming this is your own board...
- What is the target MCU?
LPC1114/301

- What pull-ups are you using on the MCU's debug related signals
none on my target, not sure on 1/2 lpcxpresson board.

- What are you doing with the ISP pin (P0.1 on an LPC11)
pulled up

- Can you provide an actual schematic of the reset/debug related portions of the board being debugged?

If it is the MCU portion of the LPCXPresso1114 board - how exactly are you connecting the probes to the board?
I rigged up a a connector to SWDIO, SWCLK, RESET, pwr, and gnd.

It might also be helpful if you could provide the debug logs from your attempts to connect to the board with both RedProbe+ and LPC-Link.
Not much there:
LPCXpresso Debug Driver v4.0 (Sep 21 2011 20:05:54)
Looked for chip XML file in C:/nxp/LPCXpresso_4.1.0_190/lpcxpresso/bin/LPC1114/301.xml
Looked for vendor directory XML file in

http://support.code-red-tech.com/CodeRedWiki/DebugLog

Regards,
CodeRedSupport

Thank you very much, see above.

Rich

lpcware · ‎06-15-2016

Content originally posted in LPCWare by richas on Thu Dec 01 10:18:12 MST 2011

Quote: SteveClevenger
The setting I've used is Debug Configurations -> Debugger -> Maximum wire speed.

I found it, thank you. This is the kind of thing I HATE. Yesterday I tried slower and slower "wire speeds" and got a different error, related to wire errors...

This morning I tried it and it works! (ugh) Any wire speed setting (even 30000) besides the "empty" default setting works. Setting it back to the empty default repeatedly causes it to fail.

Rich

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Thu Dec 01 06:07:22 MST 2011
In addition to trying out changing the wire speed as suggested by the previous poster, can you please confirm:

- What actually is your target board? Is it the MCU portion of an LPCXPresso 1114 board that you have split into 2, or is it a board of your own design?

Assuming this is your own board...
- What is the target MCU?
- What pull-ups are you using on the MCU's debug related signals
- What are you doing with the ISP pin (P0.1 on an LPC11)
- Can you provide an actual schematic of the reset/debug related portions of the board being debugged?

If it is the MCU portion of the LPCXPresso1114 board - how exactly are you connecting the probes to the board?

It might also be helpful if you could provide the debug logs from your attempts to connect to the board with both RedProbe+ and LPC-Link.

http://support.code-red-tech.com/CodeRedWiki/DebugLog

Regards,
CodeRedSupport

lpcware · ‎06-15-2016

Content originally posted in LPCWare by SteveClevenger on Wed Nov 30 23:23:40 MST 2011

Quote: richas
Where is this setting?

v4.1.0 build 190

The setting I've used is Debug Configurations -> Debugger -> Maximum wire speed.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by richas on Wed Nov 30 16:40:38 MST 2011

Quote: SteveClevenger
As an experiment, connect your Red Probe+. The wire speed defaults to 3000 KHz. Try 1000 KHz in your Debug Configuration, and report your results. Also, what LPCXpresso installation are you running? There are no prior Win32 exceptions reported against the latest version.

Where is this setting?

v4.1.0 build 190

lpcware · ‎06-15-2016

Content originally posted in LPCWare by SteveClevenger on Wed Nov 30 15:55:03 MST 2011

Quote: richas
For now I have cobbled the LPC-Link debugger to our target and am using that. It is too bad as the Red Probe seemed to download faster.........
Rich

As an experiment, connect your Red Probe+. The wire speed defaults to 3000 KHz. Try 1000 KHz in your Debug Configuration, and report your results. Also, what LPCXpresso installation are you running? There are no prior Win32 exceptions reported against the latest version.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by richas on Wed Nov 30 14:50:28 MST 2011
For now I have cobbled the LPC-Link debugger to our target and am using that. It is too bad as the Red Probe seemed to download faster.........

Rich

lpcware · ‎06-15-2016

Content originally posted in LPCWare by richas on Wed Nov 30 14:32:04 MST 2011
Well this problem is back and no amount of uninstall/reinstall or rebooting will fix it. Attached are images of the errors.

Rich

lpcware · ‎06-15-2016

Content originally posted in LPCWare by richas on Thu Nov 17 11:33:29 MST 2011
Uninstalling/installing LPCxpresso fixed it. :P

lpcware · ‎06-15-2016

Content originally posted in LPCWare by richas on Thu Nov 17 10:25:24 MST 2011

Quote: TheFallGuy
Which host OS are you using? And which version of LPCXpresso?

WinXP, and LPCxpresso 4.1.0

Thanks

Rich

lpcware · ‎06-15-2016

Content originally posted in LPCWare by richas on Thu Nov 17 10:24:41 MST 2011

Quote: CodeRedSupport
You mean the LPC-Link probe, and not the Red Probe+? I see the necessary GND connections, but you didn't specify where the GND is. The Red Probe+ samples Vtref (pin 1) to adjust the logic level. If you're not sharing GND with your LPCXpresso board, this can be a source of trouble. Usually, the LPCXpresso IDE will complain about a wire error (invalid ACK, etc.) rather than report a disconnect.

Regards,

CodeRedSupport

? I am using bothe the LPC Link (1/2 of the LPCxpresso board) AND the Red Probe. LPC Link works, Red probe does not.

Like I listed in the first post:

GND to pin 2,4,6,8,10,12,14,16,18, and 20
vcc to pin 1
SWDIO to pin 7
SWCLK to pin 9
reset to pin 15

The power led on the probe+ lights.

The Target LED also lights when the target is powered.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by TheFallGuy on Thu Nov 17 02:30:12 MST 2011
Which host OS are you using? And which version of LPCXpresso?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Wed Nov 16 19:39:31 MST 2011

Quote: richas
Interestingly, I can program the part with the probe........

Rich

You mean the LPC-Link probe, and not the Red Probe+? I see the necessary GND connections, but you didn't specify where the GND is. The Red Probe+ samples Vtref (pin 1) to adjust the logic level. If you're not sharing GND with your LPCXpresso board, this can be a source of trouble. Usually, the LPCXpresso IDE will complain about a wire error (invalid ACK, etc.) rather than report a disconnect.

Regards,

CodeRedSupport

lpcware · ‎06-15-2016

Content originally posted in LPCWare by richas on Wed Nov 16 17:06:10 MST 2011
Interestingly, I can program the part with the probe........

Rich