LPC link and LPC linkII with IDE 772

[lpcware]

Content originally posted in LPCWare by PoolCop on Fri May 29 07:48:46 MST 2015
Hello,

quite a newbie with LPCXpresso and debug probes...

host W7 SP1 64bits
IDE LPCXpresso V7.7.2 (buid 379)
target MCU: custom board with LPC1768

I'm using LPC Link (with LPC3154) on 2 differents custom boards, I always get the same Em(01) error. I can see the custom board having a reset (so it is powered!) but download do not start.
Probe driver seems ok, declared as "LPC-Link Probe v1.3" on computer.
In Debug Configurations, Debug protocol is 'none', emulator is 'LPC-Link (HID)'
got this error:

LPCXpresso Debug Driver v7.7 (Mar 31 2015 21:04:28 - crt_emu_cm3_nxp build 93)
Failed on connect: Em(01). Cannot find selected MEM-AP (check target power)
Conn&Reset. Was: None. CpuID: 00000000. Info: HID64HS12
Error 0: (null)
Last sticky: 8. AIndex: 0
No MemAp selected
No Speed test
Debug protocol: SWD Frequency 3000 KHz. RTCK: Disabled. Vector catch: Disabled.
(100) Target Connection Failed


I thought my LPC Link probe may had been damaged, So I ordered a LPC LinkII board ( with LPC4370)
Trying to debug with the same custom targets give the following:

Probe driver is declared as "LPC-LINK2 REDLINK" but show an error (10) 'cannot start'
In Debug configurations, Debug protocol is 'none', emulator is 'Redlink Server'.
This time I got a timeout during "initializing Redlink Server with LPC432x_Redlink_V5_100.bin.hdr"
and then obviously "timeout booting Redlink device"

Is the LPC432x Redlink correct for LPC4370 ?
I guess something is wrong with my settings but connot figure out what...
I also saw some topics around WIN32 /WIN64 directories..

can someone help ?
Thanks

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Wed Jun 03 03:00:46 MST 2015

---

Quote:
this device cannot start(Code 10)

---

My guess is that your USB port/hub cannot cope with the total bandwidth required and is Windows is refusing to allow the driver to boot correctly. Try connecting to directly to a different USB port (no hub). If this still does not resolve the problem, you can change the LPC-Link firmware that is soft-booted to a version that reduces the bandwidth required (by not supporting some of the additional functionality). See the FAQ: http://www.lpcware.com/content/faq/lpcxpresso/configuring-lpc-link2-firmware-soft-load for information.

Details:
In LPCXpresso 7.7.x and later, we added several endpoints to the Redlink and CMSIS-DAP firmware images for LPC-Link2, to allow us to obtain the additional  data required by SWO Trace and the Power Measurement tools. When these additional endpoints enumerate, Windows 'reserves' USB bandwidth (even if it is not used). Windows then calculates the total bandwidth required by all devices (and endpoints) connected to a hub (both internal and external hubs) and will refuse to allow the device driver to boot if the USB bandwidth is exceeded. If this happens, try different USB ports, or use one of the 'debug only' variants of the firmware, as described in the FAQ (above)

[lpcware]

Content originally posted in LPCWare by R2D2 on Tue Jun 02 10:33:52 MST 2015

---

Quote: PoolCop
I do not suspect he 64bits machine to be the issue because, so far, my 'old' LPC Link1 probe was running fine.

---

Updating to V7.8.0 could be a good idea. Then LPCXpresso is trying to use CMSIS-DAP...

But anyway, the easiest approach is to delete your MCU with FlashMagic...

[lpcware]

Content originally posted in LPCWare by LessThanZero on Tue Jun 02 10:04:15 MST 2015

I ran into a similar problem. Rebooting your computer should resolve this. I later uninstalled the device, then reinstalled with the device drivers supplied in the LPCXpresso_7.7.2_379 release. I haven't seen a problem since. I've installed LPCXpresso_7.8.0_426 (released today), and everything works as advertised.

LessThanZero.

[lpcware]

Content originally posted in LPCWare by TheFallGuy on Tue Jun 02 09:52:23 MST 2015
Try updating the drivers. In device manager, find th device, right-click and update. If that does not do anything, delete the driver, removing it from the system.

[lpcware]

Content originally posted in LPCWare by PoolCop on Tue Jun 02 09:34:02 MST 2015
Thanks R2D2,

my laptop is running W7 SP1/64bits

Trying to boot the probe manually was a check suggested by the hint: http://www.lpcware.com/content/faq/lpcxpresso/booting-lpc-link2.
Apparently the driver is loaded but cannot start. code(10).
I do not suspect he 64bits machine to be the issue because, so far, my 'old' LPC Link1 probe was running fine.

[lpcware]

Content originally posted in LPCWare by R2D2 on Tue Jun 02 02:22:23 MST 2015

---

Quote: PoolCop
Still wondering if LPC432x driver is correct for LPC4370 ?

---

Yes  :)

[img=470x56]http://www.lpcware.com/system/files/Boot.JPG[/img]

(OS: Win8.1/64)

I'm not sure what you are doing in detail  :~

How did you connect Link2 with your boards?

Did you try to use another PC?

Could be useful to post pictures or a video...

[lpcware]

Content originally posted in LPCWare by PoolCop on Tue Jun 02 01:45:34 MST 2015
Addendum:

command is actually:
c:\nxp\LPC\lpcxpresso\bin>boot_link2.

Still wondering if LPC432x driver is correct for LPC4370 ?

[lpcware]

Content originally posted in LPCWare by PoolCop on Tue Jun 02 01:42:58 MST 2015
Hello,

I followed both hardware and booting hints on LPC Link II probe.
I've added the pull up resistors on SWO and SWDO as required, but without effect. I also tried ISP on target MCU, no change.
I then try to dig a bit on driver side: when booting from command line, all seems ok:
c:\nxp\LPC\lpcxpresso\bin>boot
Booting LPC-Link2 with LPC432x
LPC-Link2 booted

After Booting, Link II probe appears as "LPC-LINK2 REDLINK" but shows an error:
this device cannot start(Code 10) ....translate from French, english text should be exactly the same....

I guess this is the same issue preventing the IDE to start the probe...

So no progress so far....

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Mon Jun 01 07:24:49 MST 2015
The debug connection pretty much relies upon you having correctly working hardware - and if you don't you can get all sorts of strange effects. So as I said previously, check your hardware first.

But to check for issues on your host computer too, you might want to try booting your debug probes manually...

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

and in particular go through the troubleshooting section towards the bottom.

Regards,
LPCXpresso Support

[lpcware]

Content originally posted in LPCWare by PoolCop on Mon Jun 01 00:51:16 MST 2015
Hello,

thanks for helping, I will check the debug design.
Can this explain why the RedLink server cannot initialize?

Rgds

[lpcware]

Content originally posted in LPCWare by PoolCop on Sun May 31 23:34:35 MST 2015
Hi R2D2,

Yes the boards are running they own code, downloading via USB, so flash mem is ok
Thks

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Fri May 29 11:12:00 MST 2015
In the first place, as these are custom boards - check your debug/reset circuitry...

http://www.lpcware.com/content/faq/lpcxpresso/debug-design

Regards,
LPCXpresso Support

[lpcware]

Content originally posted in LPCWare by R2D2 on Fri May 29 08:11:29 MST 2015

---

Quote: PoolCop
...on 2 differents custom boards...

---

Could you flash them before?

Are you sure that they are working at all?