updated 5.2.6 to 6.1.0 debugger problem

[lpcware]

Content originally posted in LPCWare by ASCOTJan-H on Tue Dec 10 02:07:00 MST 2013
Hello everybody,

I did recently updated my LPCXpresso from version 5.2.6_2137 to 6.1.2_177. Now I can't launch the debugger for any of my old and new projects. The Application loads to 94% and stops with a error.
Error code:
"Error in final launch sequence
  Failed to execute MI command:
-target-select extended-remote | crt_emu_cm3_nxp -msg-port=51273 -g -mi -2 -pLPC1769 -vendor=NXP -e0 -wire=hid -flash-driver=LPC175x_6x_512.cfx
Error message from debugger back end:
Remote communication error.  Target disconnected.: No error.
  Remote communication error.  Target disconnected.: No error."
I used the LPCXpresso LPC1769 REV B board in this example, but I have this issue with other lpc as well e.g. lpc11xx.

If I downgrade my LPCXpresso version to 5.2.6, it is working again. I already tried to remove all old driver for the LPC-Link, cleaning the projects and creating new clean projects in a different workspace. I'm right now clueless what is causing this problem. I hope somebody can help me out with this problem.

Best regards
Jan-H.

[lpcware]

Content originally posted in LPCWare by ASCOTJan-H on Tue Dec 10 07:25:42 MST 2013
Thank you,
the problem was caused by the avast firewall. Somehow the rule for LPCXpresso is not working.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Tue Dec 10 07:06:00 MST 2013
Note that (apart from being signed with a new certificate) the actual driver "USB Device with DFU capabilities" has not been changed in any way since the very first release of LPCXpresso, 4 years ago. i.e. uninstall and reinstall will make no difference whatsoever.

Also, that driver is ONLY used when booting LPC-Link. You are not having any problems booting it, so that is not the problem.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Tue Dec 10 07:04:48 MST 2013
One other thought is the Firewall.

One difference between what you are doing from the command line vs the IDE is the "-msgport=" option. This is a communication channel between the debug driver and the IDE. It uses a socket interface (with the port specified in the option). The port is created dynamically by the IDE (and so the port number will be different for every debug session).

It is possible that the IDE or the debug driver (crt_emu...exe) is being blocked from accessing the port. You might want to take a look at your firewall configuration and make sure that the IDE and the debug driver are allowed to access the socket.

[lpcware]

Content originally posted in LPCWare by ASCOTJan-H on Tue Dec 10 06:55:19 MST 2013
I did try different USB ports, including docking station USB ports.
I did suspected the driver as well and uninstalled the LPCXpresso IDE and manual removing the .\Windows\System32\drivers\MassDfu64.sys driver. The new Installation did add the file again. Also I did installed it as admin.
I did also tried to reinstall the driver.
The debugger appears as  "USB Device with DFU Capabilities".

If I uninstall 6.1.x and install 5.2.6 it is working.
You can also contact me via skype and we could do some screen sharing.

[lpcware]

Content originally posted in LPCWare by bavarian on Tue Dec 10 06:36:04 MST 2013
Without being able to prove it now: it sounds like a communication problem between the PC and the debugger chip on the LPCXpresso board.

Did you maybe try to work on a different USB port, or with a hub inbetween?
Have you installed the new version with admin rights, in order to get maybe the USB driver updated (debugger appears as "USB Device with DFU Capabilities", driver is MassDfu64.sys) ?

Regards,
NXP Support Team

[lpcware]

Content originally posted in LPCWare by ASCOTJan-H on Tue Dec 10 04:56:33 MST 2013
I'm confused as well.

I did add to my system environment variable the path to the bin folder, did not help.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Tue Dec 10 04:31:00 MST 2013
So that works...

How about erasing the flash on your target? Type:

crt_emu_cm3_nxp -flash-mass -g -2 -vendor=NXP -pLPC1768  -wire=hid -s250  -flash-driver=LPC175x_6x_32.cfx

And if that works, try this

crt_emu_cm3_nxp -flash-mass -g -2 -vendor=NXP -pLPC1768  -wire=hid -s250  -flash-driver=LPC175x_6x_32.cfx -e0

If these work, you could try the same thing from within the IDE, by pressing the Program Flash button in the toolbar.

As you can probably tell, we are really confused by this...

[lpcware]

Content originally posted in LPCWare by ASCOTJan-H on Tue Dec 10 04:04:50 MST 2013
Hit post twice...

[lpcware]

Content originally posted in LPCWare by ASCOTJan-H on Tue Dec 10 04:04:01 MST 2013
I did try another NXP LPC-link as well, same problem.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Tue Dec 10 03:53:09 MST 2013
Please try running this from the command line:

crt_emu_cm3_nxp -g -mi -wire=hid -info-emu

if this works, then try

crt_emu_cm3_nxp -g -mi -wire=hid -pLPC1769 -vendor=NXP -info-target

Please post the the results of running these commands.

Note: LPC-Link must be booted to run this - if it is not, go to the bin/Scripts directory and run

bootLPCXpresso hid

[lpcware]

Content originally posted in LPCWare by ASCOTJan-H on Tue Dec 10 03:44:27 MST 2013
I'm using the uart example from the "examples.lpc17xx.new.zip" archive.
ISP <- don't help. I already had tried 5 different LPC, I each with different firmware.
Debug Log see attachment, I only did add not empty logs.
empty logs:
- debug messages
- debug [C/C++ (NXP Semiconductors)MCU Application] gdb

Host <- You mean my OS?
Windows 7 Version 6.1 (Build 7601:Service Pack1)

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Tue Dec 10 03:09:51 MST 2013
A few things for you to try.

[list]
  [*]Can you try one of the supplied examples for the LPC1769 LPCXpresso board
  [*]Please try booting the target into ISP mode: http://www.lpcware.com/content/faq/lpcxpresso/regaining-debug-access
  [*]Please supply the contents of the Debug Log : http://www.lpcware.com/content/faq/lpcxpresso/debug-log
  [*]Please state which Host you are running on, and the version number
[/list]

[lpcware]

Content originally posted in LPCWare by ASCOTJan-H on Tue Dec 10 02:46:38 MST 2013
I already did try removing the launch configuration. The problem persist. Also it does persist, if I create a new project in a new workspace. If the the launch configuration would causing this problem, it would work with a new clean project ;). I don't believe the project setup is causing it, but feel free to prove me wrong.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Tue Dec 10 02:31:34 MST 2013
Try deleting and recreating the Launch (Debug) configuration. RIght-click on the project and select Launch configuration->Delete current. To start a debug session, just press the Debug button in the Quickstart panel.