LPCXpresso v7.9.0 can't connect to LPC - Link2

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Elianco_ES on Tue Sep 01 11:48:21 MST 2015
Hello Tech support,

I just installed LPCXpresso v7.9.0 [Build 455] [2015-07-23] and after compiling and building the project

the new version can't connect to my LPC - Link2 debugger/downloader.

After several trials and also re-connecting the USB cable it just can't find the LPC - Link2 debugger/downloader. The windows control manager shows that the LPC-Link2 CMSIS-Dap V5.112

is connected and driver is installed.

The older version LPCXpresso v7.4.0 works fine. I can download the program and single step it with no problem.

Please let me know how to fix this problem.

Thanks,

lpcware · ‎06-15-2016

Content originally posted in LPCWare by gleeuwrik on Fri Oct 23 07:04:26 MST 2015
You da man. Your sequence worked!

Thanks for posting.

Gordon L.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Elianco_ES on Fri Sep 04 12:21:44 MST 2015

Hello LPCXpresso Support, TheFallGuy and robert hulsebos.

Thanks for your reply and suggestions.

I checked the Windows paths.

I found the cscript.exe and wmic.exe in the C:\Windows\System32 directory.

I also run boot_link2 command and got a message "Nothing to boot".

I can still use the same LPC Link2 with LPCXpresso IDE : v7.4 and it works fine.

But it doesn't work with LPCXpresso IDE : v7.9.0.

Maybe I should uninstall LPCXpresso IDE : v7.4?

Thanks ,

Best Regards.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by robert hulsebos on Fri Sep 04 02:39:24 MST 2015
I had similar problems. What eventually helped for me was the combination of the following 4 steps:

1. Deleting the .launch files from the project directory.

2. Also I had to force the re-detection of emulator by setting emulator selection to <none>. Procedure: Right click on your debug project in Project Explorer window | Properties | Run/Debug Settings | <select correct debug project> | Edit button | <select Debugger tab>
In this window you must set 'Emulator selection' to '<none>'.

3. Also in the same window, under Debugging Options, Target Configuration tab, make sure the 'Vector catch' option is set to TRUE.

4. Power cycle on emulator. (e.g. disconnecting/re-connecting USB from link2 board)

This worked for me...

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Thu Sep 03 09:58:59 MST 2015

Do read the link above regarding the Windows paths. The LPC device VID:PID shows up in the list, and this is proof the CMSIS-DAP probe did not boot.

Thanks and regards,
LPCXpresso Support

lpcware · ‎06-15-2016

Content originally posted in LPCWare by TheFallGuy on Thu Sep 03 09:45:41 MST 2015
Have you tried this?
https://www.lpcware.com/content/faq/lpcxpresso/windows-path-issues

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Elianco_ES on Thu Sep 03 09:35:24 MST 2015
Hello lpcxpresso-support,

Thanks for your reply and your help.

Here is the output after running "usbdiags" program:

Tasks:

Image Name                     PID Services
========================= ======== ============================================
System Idle Process              0 N/A
System                           4 N/A
smss.exe                       236 N/A
csrss.exe                      336 N/A
wininit.exe                    396 N/A
csrss.exe                      412 N/A
services.exe                   460 N/A
lsass.exe                      476 Netlogon, SamSs
lsm.exe                        484 N/A
winlogon.exe                   540 N/A
svchost.exe                    656 DcomLaunch, PlugPlay, Power
nvvsvc.exe                     748 NVSvc
nvSCPAPISvr.exe                772 Stereo Service
svchost.exe                    820 RpcEptMapper, RpcSs
svchost.exe                    872 Audiosrv, Dhcp, eventlog, lmhosts, wscsvc
svchost.exe                    964 AudioEndpointBuilder, CscService, Netman,
                                   PcaSvc, SysMain, TrkWks, UxSms, wudfsvc
svchost.exe                    992 EventSystem, FontCache, netprofm, nsi,
                                   W32Time, WdiServiceHost, WinHttpAutoProxySv
svchost.exe                   1032 AeLookupSvc, Appinfo, BITS, Browser,
                                   IKEEXT, iphlpsvc, LanmanServer, ProfSvc,
                                   Schedule, SENS, ShellHWDetection, Themes,
                                   Winmgmt, wuauserv
svchost.exe                   1144 gpsvc
svchost.exe                   1272 CryptSvc, Dnscache, LanmanWorkstation,
                                   NlaSvc
spoolsv.exe                   1384 Spooler
NvXDSync.exe                  1440 N/A
nvvsvc.exe                    1448 N/A
svchost.exe                   1512 BFE, DPS, MpsSvc
armsvc.exe                    1792 AdobeARMservice
g2ax_service.exe              1872 GoToAssist Remote Support Customer
dmwu.exe                      1968 IBUpdaterService
MSOIDSVC.EXE                  1992 msoidsvc
NTRtScan.exe                   268 ntrtscan
svchost.exe                    332 RemoteRegistry
snmptrap.exe                   392 SNMPTRAP
svchost.exe                    572 StiSvc
ToolbarUpdater.exe            1092 vToolbarUpdater18.8.0
MSOIDSVCM.EXE                  652 N/A
loggingserver.exe             1824 N/A
TmListen.exe                  1844 tmlisten
conhost.exe                   2032 N/A
WmiPrvSE.exe                  2224 N/A
g2ax_comm_customer.exe        2432 N/A
g2ax_system_customer.exe      2552 N/A
svchost.exe                   2796 PolicyAgent
svchost.exe                   2820 WinDefend
WmiPrvSE.exe                  2984 N/A
TmProxy.exe                   3428 TmProxy
CNTAoSMgr.exe                 3756 N/A
conhost.exe                   3764 N/A
taskhost.exe                  3900 N/A
dwm.exe                       3936 N/A
explorer.exe                  3968 N/A
g2ax_user_customer.exe        3976 N/A
PccNTMon.exe                  3616 N/A
vprot.exe                     3988 N/A
Updater.exe                   4036 N/A
dnkt.exe                      3224 N/A
jusched.exe                   2308 N/A
AmazingVisioEasyPublish.e     3180 N/A
nvtray.exe                    1028 N/A
SearchIndexer.exe             3932 WSearch
TMBMSRV.exe                   3592 TMBMServer
LMS.exe                       5152 LMS
svchost.exe                   5180 SSDPSRV
UNS.exe                       6116 UNS
jucheck.exe                   4376 N/A
firefox.exe                    936 N/A
notepad.exe                   1288 N/A
iexplore.exe                  2644 N/A
iexplore.exe                   456 N/A
FlashUtil32_18_0_0_232_Ac     4528 N/A
iexplore.exe                  5136 N/A
taskhost.exe                  5972 N/A
lpcxpresso.exe                5984 N/A
cmd.exe                       2256 N/A
conhost.exe                   2596 N/A
MpCmdRun.exe                  1264 N/A
tasklist.exe                  2704 N/A
USB Devices:
VID: 8087 PID: 0024 (Generic USB Hub)
VID: 1FC9 PID: 000C (LPC based USB device)
VID: 413C PID: 2107 (HID Keyboard Device)
VID: 0461 PID: 4D22 (USB Input Device)
VID: 413C PID: 2107 (USB Input Device)
VID: 0461 PID: 4D22 (HID-compliant mouse)
VID: 0424 PID: 2514 (Generic USB Hub)
VID: 8087 PID: 0024 (Generic USB Hub)
DFU Devices:
HID Devices:
Class GUID: {4d36e96b-e325-11ce-bfc1-08002be10318}
Description: HID Keyboard Device
Device ID: HID\VID_413C&PID_2107\7&57AFCCB&0&0000
Manufacturer: (Standard keyboards)
Name: HID Keyboard Device
PNP Device ID: HID\VID_413C&PID_2107\7&57AFCCB&0&0000
Service: kbdhid
Class GUID: {4d36e96f-e325-11ce-bfc1-08002be10318}
Description: HID-compliant mouse
Device ID: HID\VID_0461&PID_4D22\7&24A724D9&0&0000
Manufacturer: Microsoft
Name: HID-compliant mouse
PNP Device ID: HID\VID_0461&PID_4D22\7&24A724D9&0&0000
Service: mouhid

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Wed Sep 02 14:07:56 MST 2015
Please can you go through all of the Troubleshooting suggestions in the FAQ I previously pointed you at (https://www.lpcware.com/content/faq/lpcxpresso/booting-lpc-link2).

If none of those help, please try removing all non-essential USB devices from your system, then try using LPC-Link2 again.

And if that still doesn't help, then after a failure for LPCXpresso to find the probe for a debug session, please open a DOS command prompt and run the command:

{install_dir}\lpcxpresso\bin\Scripts\usbdiags > diag.txt

(where {install_dir} is your LPCXpresso 7.9.0 installation directory)

And post the diag.txt file that is generated for us to look at.

Regards,
LPCXpresso Support

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Elianco_ES on Wed Sep 02 11:58:28 MST 2015

Hello lpcxpresso-support,

Thanks for your reply.

My PC is running Window 7 OS.

I'm using LPCXpresso v7.9.0. IDE which I downloaded yesterday.

I just re-installed LPC driver and when I plugin LPC Link2 board thru USB port,

the device manager displays LPC - LINK2 CMSIS - DAP V5.112.

When I start the debugging session the LPCExpresso displays window with the following message:

No compatible emulators available.
They may be disconnected, not powered, already in use or not compatible with this target.

I stopped the debug session. Closed/re-opened LPCExpresso IDE.

Restart the debugging session the LPCExpresso displays window with the following message:

No compatible emulators available.
They may be disconnected, not powered, already in use or not compatible with this target.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Wed Sep 02 09:44:23 MST 2015
Go through the below FAQ, in particular the Troubleshooting section, and report what you actually see (both as you boot the probe and also from the IDE when you try to connect).

https://www.lpcware.com/content/faq/lpcxpresso/booting-lpc-link2

Can you also confirm what OS are you running?

Regards,
LPCXpresso Support

lpcware · ‎06-15-2016

Content originally posted in LPCWare by R2D2 on Wed Sep 02 09:42:47 MST 2015
Did you read

https://www.lpcware.com/content/faq/lpcxpresso/booting-lpc-link2

also?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Elianco_ES on Wed Sep 02 09:38:12 MST 2015

Hello R2D2,

Thanks for your reply.

I checked if the driver was the obsolete 1.0.0.0 LPC-LinkII UCOM driver.

And it was not the case.

So I still need help resolving this problem.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by R2D2 on Tue Sep 01 11:56:55 MST 2015
Did you read:

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