Error connecting to Red Probe+

[lpcware]

Content originally posted in LPCWare by dluksenberg on Tue Mar 29 08:25:29 MST 2011
I'm using a Olimex LPC1766-STK with LPCExpresso 3.6 and a Red Probe+ running WinXP SP3. When I try to debug the device I get the following error messages in the IDE:

Pop Up:
Error launching Debug\adc_buzzer.axf
02: Failed on connect: Ee(02). Not connected to emulator.:

Console:
LPCXpresso Debug Driver v2.0 (Jan 18 2011 08:08:34)
Looked for chip XML file in C:/nxp/lpcxpresso_3.6/bin/LPC1766.xml
Looked for vendor directory XML file in C:/nxp/lpcxpresso_3.6/bin/nxp_directory.xml
Found generic directory XML file in C:/nxp/lpcxpresso_3.6/bin/crt_directory.xml
02: Failed on connect: Ee(02). Not connected to emulator.
Emu(1): Connected. Was: None. DpID:     EDB6. Info: FTU349ZBA

============

Looking in device manager I have the following 3 devices installed:
USB Controllers:
Red Probe+ A
- FTDI
- Load VCP not checked
- Driver: FTDI 2.6.2.0 3/30/2010
- USB\VID_21BD
- PID_0003
- MI_00\6
- 1EA20885&0&0000

Red Probe+ B
- FTDI
- Load VCP  checked
- Driver: FTDI 2.6.2.0 3/30/2010
- USB\VID_21BD
- PID_0003
- MI_01\6
- 1EA20885&0&0001

Ports:
Red Prob+ Trace Port(COM3)
- FTDI
- Driver: FTDI 2.6.0.0 10/22/2009
- FTDIBUS\VID_21BD
- PID_0003
- FTU349ZBB\7&312276B3&1&0000

Using LibUSB I got the following info:
vid:21bd pid:0003 rev:0700 mi:01 -- Red Probe+ B
vid:21bd pid:0003 rev:0700 mi:01 -- Red Probe+ A
vid:21bd pid:0003 rev:0700       -- USB Composite Device

Is a device not installed properly?

Thanks for the help,
Dave

[lpcware]

Content originally posted in LPCWare by dluksenberg on Tue Mar 29 12:33:11 MST 2011
This makes me feel really dumb but it was power... The board can run off of USB so I assumed a 5V wall wart would work. The power LEDs on the board and probe were lit. Apparently the voltage drop across the rectifier and LDO is too high. Works great now!

Thank you,
Dave

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Tue Mar 29 11:17:56 MST 2011

---

Quote: dluksenberg
http://support.code-red-tech.com/CodeRedWiki/FailedToConnect

"Initialise LPC-Link as HID" was not checked. I closed the IDE, cycled power to the target and the probe but got the same error.

Are there any diagnostic utilities that I can run? Does the DFUAPP utility apply to the red probe?

---

The Red Probe+ (RP+) is not an LPC-Link, and it uses different device drivers. In your case, the RP+ drivers appear to have installed properly. To prove the debug utility can recognize the RP+, issue the following from a command prompt.

C:\nxp\lpcxpresso_3.6\bin>crt_emu_lpc11_13_nxp.exe -info-emu
Ni: LPCXpresso Debug Driver v2.0 (Jan 18 2011 08:09:09)
1 Emulators available:
0. FTTMPRROA    Red Probe+ A (Code Red - Red Probe+)

If you get this far, check your target power and debug connections, because target debug access is not there:

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

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

[lpcware]

Content originally posted in LPCWare by dluksenberg on Tue Mar 29 08:56:45 MST 2011
http://support.code-red-tech.com/CodeRedWiki/FailedToConnect

"Initialise LPC-Link as HID" was not checked. I closed the IDE, cycled power to the target and the probe but got the same error.

Are there any diagnostic utilities that I can run? Does the DFUAPP utility apply to the red probe?