topic Re: Major problems with LPC-LINK2 in LPCXpresso IDE

Major problems with LPC-LINK2

lpcware — Wed, 15 Jun 2016 23:23:53 GMT

Content originally posted in LPCWare by acelink1 on Tue Feb 25 23:26:44 MST 2014
Hi Guys, please help me with this. I'm new to NXP micro controllers.
I bought the LPC4357 Developers Kit, installed the latest Xpresso IDE.
Installed the USB drivers so I can program the flash via the USB.

Loaded and built the Blinky program for LPC4357 and then build. Build ok with no problems at all.
Then I tried to download to the LPC board via USB. I installed the USB drivers from NXP site ( I think ).

ERROR !!! - That wouldn't work. So I watch a video on Youtube from NXP about the LPC-LINK 2 board.

I thought that's easy enough and LPC-LINK 2 is fully supported in Xpresso. So I ordered the LPC-LINK 2 and received
it today.

Connected it up, built Blinky in XPRESSO and tried to download to flash and ERROR !!! Still does not work.

Can support please let me know what I am dong wrong to download the .AXF file to the LPC4357 board.
Here's what I do.

1. Build Blinky Program. - This builds fine, no errors.
2. RIGHT CLICK on BINARIES / Blinky.AXF file and then choose BINARY UTILITIES and then choose PROGRAM FLASH.

Next comes up a window (WINXP). At the top it says PROGRAM TARGET FLASH: LPC4xxx (NXP4357)
PROGRAM FLASH USING LPCLINK2 Redlink.

Then I look in the flash file box and Blinky.AXF is there, so it knows where the file is.

Then I hit OK to download the flash and I get this message:
ERROR: 02 FAILED TO CONNECT: Ep(01). Target marked as not debuggable.

I'm not trying to debug it I just want to program the LPC4357.

CONNECTION:
I've connected the 10pin programming cable that came with the LPC-LINK2 board to the
10 pos debug connector (J7) on the OEM BASE BOARD. Pin 1 matches with pin 1 on the cable.

Is that correct?

I am new to LPC4357 but very experienced in ATMEL MPU's.

Please let me know what I am doing wrong. I have already spent A LOT of money on this.

Thanks for your support guys.

Pete.

Re: Major problems with LPC-LINK2

lpcware — Wed, 15 Jun 2016 23:23:54 GMT

Content originally posted in LPCWare by lpcxpresso-support on Tue Feb 25 23:36:09 MST 2014
Please read this FAQ:
http://www.lpcware.com/content/faq/lpcxpresso/target-marked-not-debuggable

My guess is that you are not supplying sufficient power to the baseboard.

Re: Major problems with LPC-LINK2

lpcware — Wed, 15 Jun 2016 23:23:55 GMT

Content originally posted in LPCWare by acelink1 on Wed Feb 26 00:58:25 MST 2014
Thank you for your reply. I really need help on this one.

I'm supplying power to the Base board via the USB port (J25) directly from my PC.

Now when I try and download to flash mem I get this error.

02: FAILED ON CONNECT: Ee(36) Could not connect to core.

Do I have to change a few jumpers on the OEM BOARD or something else?

I'm truly sorry if I sound daft.

Please let me know.

Thanks Support :)
Pete

Re: Major problems with LPC-LINK2

lpcware — Wed, 15 Jun 2016 23:23:55 GMT

Content originally posted in LPCWare by rocketdawg on Wed Feb 26 09:15:47 MST 2014
perhaps a driver problem related to WinXP?
you probably need Service Pack 3 or greater.

Do you see the LPC device in the device manager? And what are the drivers loaded for the device?

I have no problems whatsoever on Win 7. I know, doesn't help you, but that is why I think it is a device driver problem

Re: Major problems with LPC-LINK2

lpcware — Wed, 15 Jun 2016 23:23:56 GMT

Content originally posted in LPCWare by skw0 on Wed Feb 26 13:12:51 MST 2014
I had a similar problem when I started out with the lpcxpresso and XP.

The thing that fixed it for me was to install the Microsoft C++ 2008 redistributable package (vcredist_x86.exe). (I think there was a message in the XP event log but I've slept since then)

Hope that helps

Re: Major problems with LPC-LINK2

lpcware — Wed, 15 Jun 2016 23:23:57 GMT

Content originally posted in LPCWare by acelink1 on Wed Feb 26 15:15:02 MST 2014
Thanks everyone for the excellent support. But the problem was a jumper not shorted to enable the JTAG port on the OEM Board.

So all is good now. :)

Thanks Guys :)

Pete