LPCXpresso build 177 debugger/JTAG problems

[lpcware]

Content originally posted in LPCWare by g40 on Wed Jan 15 13:23:07 MST 2014
Apologies that my first post here is a complaint.

Sadly I am having massive problems using a Red Probe+ JTAG adapter on Windows 7 x64. The device appears to be configured correctly and is identified by the IDE, finding the right target..

I can verify that both probe and target board (EA LPC4088 Quickstart) work correctly using a toolchain from another vendor. I can also debug the .bin file created by LPCXpresso using the other product.

I'm not quite sure when the process is failing - the whole IDE locks and Task Manager shows that both crt_emu_cm3_nxp.exe and arm-none-eabi-gdb.exe are spawned but are in a zombie state. I have attached a JPEG of the dysfunctional GUI.

Insanely the console clears itself after code is downloaded to the target so I cannot even show what it reports. (Is there any way of stopping this from happening?)

Any help gratefully received. If more information is needed please ask.

BR.

Jerry

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Thu Jan 16 15:48:00 MST 2014

---

Quote: g40
Hello Support and Thanks.

The Red Probe was connected via a USB3 hub. Moving it to a USB2 hub has made things work more smoothly.

Sadly the device I am running uses a serial connection for various things and this is, of course, connected via a USB -> Serial converter. The upshot is that LPCXpresso keeps losing track of the probe, even though it is still listed as a connected device in various USB device viewers.

I take the point about the console, however the IDE does switch from one to another (apparently) automatically and this significantly complicates bug reporting.

Is there anything more I can do to solve the disappearing Red Probe+ problem?

Thanks again.

---

You have the ability to "pin" the debug console to prevent the console view from shifting to a console with the latest activity. You should review this forum post for clues:

http://www.lpcware.com/content/forum/usage-multiple-debug-sessions-one-pc

In particular, is your USB-Serial converter an FTDI based device? Is it possible to test using USB port(s) directly connected to your computer? Is it possible to substitute a different hub, preferably from a different manufacturer?

Regards,

LPCXpresso-Support

[lpcware]

Content originally posted in LPCWare by g40 on Thu Jan 16 13:22:59 MST 2014
Hello Support and Thanks.

The Red Probe was connected via a USB3 hub. Moving it to a USB2 hub has made things work more smoothly.

Sadly the device I am running uses a serial connection for various things and this is, of course, connected via a USB -> Serial converter. The upshot is that LPCXpresso keeps losing track of the probe, even though it is still listed as a connected device in various USB device viewers.

I take the point about the console, however the IDE does switch from one to another (apparently) automatically and this significantly complicates bug reporting.

Is there anything more I can do to solve the disappearing Red Probe+ problem?

Thanks again.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Wed Jan 15 14:30:19 MST 2014
This is not a known problem, and has not been reported before. We have thousands of customers using Red Probe+ successfully.

There are actually many consoles, and they are not cleared. Could you please post the Debug Log (console) as described here:
http://www.lpcware.com/content/faq/lpcxpresso/debug-log

Are couple of possibilities are:
[list]
  [*] if you have any USB<>Serial converters connected to your PC, please trying removing them and try debugging again
  [*] Also, please try connecting Red Probe+ to a different USB port. If your PC has USB3 and USB2 ports, please connect to the USB2 ports
[/list]

Hope that helps,