LPCLink2 program image problem

[lpcware]

Content originally posted in LPCWare by bjorn1989 on Tue May 13 13:30:54 MST 2014
hi,

I am trying to set a new image to my LPCLINK2, but I get the following error.
CMSIS-DAP LPC-Link2 debugger image

Verify program operation:

algorithm file: Simple CRC = : 1729072
Image file : Simple CRC : 1674718
Downloading programming algorithm via DFU ROM boot
DFU programming algorithm download complete
Device detected: Programming algorithm
Programming algorithm did not enter idle state

There are no jumpers connected to the board.

I did download the newest drivers from the lpcware.com.

Does someone know how I can solve this problem?

[lpcware]

Content originally posted in LPCWare by andru on Wed Mar 18 23:49:43 MST 2015
I put the jumper on the R1 MINI4357 and JTAG began working steadily.

[lpcware]

Content originally posted in LPCWare by bjorn1989 on Wed Jun 11 06:28:01 MST 2014
Hi all,

The DBGEN pin is pulled high.

I did made a simple mistake in the JTAG connection, I did put the wrong pins to the processor. did I damage the processor and Is it possible that I need to re-program the LPC4357 with Flashmagic and that it is than working properly

I did look for the ISP / boot setup. I want to erase and reprogram the processor with an UART0 connection. To setup the right boot settings I need pin P1_1, P1_2, P2_8,P2_9 to set this. But these pins are connected to the external SRAM chip and not to the I/O headers. Is there another way to re program this processor?

*
P2_0 & 2_1 are also connected to external RAM.
2_7 is routed outside to pin headers
*


I am using a Embest Mini4357 and a LPC Link2.

[lpcware]

Content originally posted in LPCWare by arw on Fri May 23 09:33:43 MST 2014
Additionally, the DBGEN pin should be pulled HIGH.
-aw

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Fri May 23 08:01:38 MST 2014
Did you read this FAQ?
http://www.lpcware.com/content/faq/lpcxpresso/debug-design

[lpcware]

Content originally posted in LPCWare by bavarian on Fri May 23 07:45:11 MST 2014
You should already see a connection between the debugger and the MCU when you go into the debugger settings.
If you don't see 2 ARM cores appearing there, you have a kind of hardware problem:

[list]
  [*]  check the 10-pin connection
  [*]  in the debugger setting use the following for the reset:   Normal + VECTRESET + Reset after connect
  [*]  put the LPC4357 into different boot modes, e.g. ISP mode, to verify if maybe a running software blocks the JTAG access
[/list]

Regards,
NXP Support Team

[lpcware]

Content originally posted in LPCWare by bjorn1989 on Tue May 20 13:41:13 MST 2014
Hi,

Thanks al for support about the image problem.

I am using a Embest Mini4357 board, I have made my own board with an Jtag connection and other stuf that I want to use.
But I have a problem with the JTAG connection, when I am trying to download the flash with Uvision I get the following message: JTAG communication failure.

I did read the user manual of the NXP LPC4357, they recommend 2 pull up resistors on the TCK and TDO. I did use this in my design. When I read the schematics of the extra board from the manufacturer, they use 4 pull up resistors.
In my opinion I only have to use 2 pull up resistors but it is not working.

What I am doing wrong?


Thanks,

Bjorn

[lpcware]

Content originally posted in LPCWare by bjorn1989 on Wed May 14 02:22:33 MST 2014
What maybe is the problem that I am using a Macbook with VMWare Fusion 6 to run Uvision 5 on windows 7.

I ask a college to instal the configuration tool and it runs without a problem. When we status Uvision, the program see the link2, when I am doing the same on my macbook, there is no device found.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Wed May 14 01:28:45 MST 2014
I am assuming you are running v7.1.1 on Windows.

Please try this:
[list]
  [*]open a command prompt in the lpcxpresso/bin/scripts directory
  [*]connect LPC-Link2
  [*]> listusb
[list]
  [*] If Windows can see the probe, you will see an entry like this:
[list]
  [*]VID: 1FC9 PID: 000C (LPC based USB device)
[/list]
[/list]
  [*]> cd ..
  [*]> dfu-util.exe -d 1fc9:000c -c 1 -t 2048 -R -D LPC432x_Redlink_V4_26.bin.hdr
  [*]> listusb
[list]
  [*] If LPC-Link2 has booted, you should see two entries:
[list]
  [*]VID: 21BD PID: 0006 (HID-compliant device)
  [*]VID: 21BD PID: 0006 (USB Input Device)
[/list]
[/list]
[/list]

Try this with the LPC-Link2 connected to different USB ports.

[lpcware]

Content originally posted in LPCWare by bjorn1989 on Wed May 14 00:30:12 MST 2014
Hi Arw,

Thanks for support!
It is a new Link2, I tested it with LPCXpresso but he cannot find the Link2.
I did try another USB cable but there is no difference.

Bjorn

[lpcware]

Content originally posted in LPCWare by arw on Tue May 13 16:10:45 MST 2014
Hi bjorn1989,
Is this a new Link2 or one that you've used previously with other images (including the DFU mode with LPCXpresso)?
Possibly the USB cable or connector is flaky, we see this sometimes.  Please check both carefully.  If you can also test using LPCXpresso that is helpful to know.
-arw