Using LPC810 board with LPC link

lpcware · ‎06-15-2016

Content originally posted in LPCWare by js-nxp on Thu Jun 20 23:59:10 MST 2013
So I managed to get Flash Magic to finally work. Ideally if I would play more with the chip I would want to use the debugger.

Am I correct in saying that I can use the LPC link which comes with the LPC1114 board?

This would mean separating the 2 boards (LPC link and LPC1114) and fitting them with connectors for future use and then use J5 connected to J1 of the LPC810 board, correct?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by js-nxp on Tue Jun 25 01:53:54 MST 2013
Ok success...well mostly. The 10 way ribbon I have was going to a breakout board which seems to swap even and odd number pins so I had to reverse it and measure it to make sure that pin was going to pin 1 etc.

Then, as suggetsed, I had to start in ISP mode because the demo code is using the LED pin, I should be able to move the LED on another pin I guess but I was able to program the chip and even start a debug session.

It worked in single step mode until the LED was turned on and then crashed.

So I'm happy :) thanks.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Tue Jun 25 00:53:25 MST 2013
As per my original reply...

Quote:
if you have code that is using the LED programmed into the flash, you will need to boot the board into ISP mode before trying to start a debug connection to it.

Regards,
CodeRedSupport

lpcware · ‎06-15-2016

Content originally posted in LPCWare by js-nxp on Mon Jun 24 16:12:11 MST 2013
Thank you.

Quote:
- you have not correctly separated LPC-Link

All 8 tracks have been measured and there is no connections between one board and the other.

Quote:
- you have not correctly wired up SWD from LPC-Link to the target

That's possible, the first attempt had only 2 wires and GND as above but not reset. However it is currently connected with the 10 way ribbon between J5 of the LPC link and J1 of the mini board, should this not result in a correct wiring?

Quote:
- the target is in one of the CRP modes

Haha no idea what that means... :) but we did have a super moon yesterday, it makes people do crazy things (like trying to use the LPC800) so it may affect the chip too....:D

Quote:
- the target is not powered

There is power on the target via a 2nd USB connector

Quote:
- the target is being held in reset

There is nothing else on the board.

However the LED is on the SWDIO/TMS pin, maybe the LPC link can't drive the load. I'll remove the resistor to free the pin and use a resistor in series with a jumper pin so that it can be restored.[FONT=Arial][SIZE=1][COLOR=#ff0000][FONT=Arial][SIZE=1][COLOR=#ff0000]
[/COLOR][/SIZE][/FONT][/COLOR][/SIZE][/FONT]

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Mon Jun 24 01:29:55 MST 2013
"target marked as not debuggable" means that the debugger/debug driver cannot 'see' the processor over SWD (or JTAG). This implies one or more of the following
- you have not correctly separated LPC-Link
- you have not correctly wired up SWD from LPC-Link to the target
- the target is in one of the CRP modes
- the target is not powered
- the target is being held in reset

lpcware · ‎06-15-2016

Content originally posted in LPCWare by R2D2 on Mon Jun 24 00:43:59 MST 2013

Quote: js-nxp
Connected GND, SWDIO and SWCLK pins between the The LPC800 mini board and the LCP link, not working. (preferred as it only uses 2 pins if correct)

Would suggest to connect Reset also (if this chip has it?).

lpcware · ‎06-15-2016

Content originally posted in LPCWare by js-nxp on Mon Jun 24 00:27:26 MST 2013
I think I have hit a brickwall. :confused: From the LPC800 Mini-Kit info I have

Quote:
The LPC800 mini board can be programmed using any SWD debugger and your favorite IDE -- NXP's own LPCXpresso

How? Any links on how to do this?

What I have done so far: Separated the LCP link from the LPC114 side of the board so that the SWD/JTAG? pins are free.

Connected GND, SWDIO and SWCLK pins between the The LPC800 mini board and the LCP link, not working. (preferred as it only uses 2 pins if correct)

Removed all other connection to the RS232 board so nothing is conneted to the mini board and connected the 2 boards with the 10 way miniature debug cable, same results as above.

Output from programmer

Quote:
Ni: LPCXpresso Debug Driver v5.2 (Apr 26 2013 19:52:11 - crt_emu_cm3_gen.exe build 1153)
Pc: ( 0) Reading remote configuration
Nc: Looked for chip XML file in C:/NXP/LPCXpresso_5.2.4_2122/lpcxpresso/bin/LPC810.xml
Nc: Looked for vendor directory XML file in C:/NXP/LPCXpresso_5.2.4_2122/lpcxpresso/bin/NXP_directory.xml
Nc: Found generic directory XML file in C:/NXP/LPCXpresso_5.2.4_2122/lpcxpresso/bin/crt_directory.xml
Pc: ( 5) Remote configuration complete
Pc: ( 15) nSRST assert (if available)
Ed:02: Failed on connect: Ep(01). Target marked as not debuggable.
Et: Emu(0): Connected. Was: None. DpID: EDB6. Info: WIN64HS12
Error 0: (null)
Last sticky: 0. AIndex: 0
No MemAp selected
No Speed test
SWD Frequency: 50 KHz. RTCK: False. Vector catch: False.
Packet delay: 0 Poll delay: 0.
Pc: (100) Target Connection Failed

Any pointer? Is this simply a matter of setting the programmer correctly?

Of course the aim is to debug and not just program but it can't do that either.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by js-nxp on Fri Jun 21 16:09:10 MST 2013
Ok the stability issue and the need to add a 3.3V regulator on the overcrowded prototyping area convinced me not to cut the board.

I just cut the tracks and soldered a 16 way header which can be jumpered either with just 3 pins (GND, 5V and 3.3V) to utilise the 3.3V regulator (5V comes from the prototyping area) or use a 16 pin PCB socket with the pins bent over and soldered to make a 8 way shunt if I need to work on the LPC114 side.

As I don't have a tiny ribbon cable for the debugger I will try and put together one using bits from another debugger which uses the same size connector.

@Leon Heller Nice to see you around. :)

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Fri Jun 21 06:37:55 MST 2013
For details of how to "split" an LPCXpresso board to allow the LPC-Link to debug an another target board see:

http://support.code-red-tech.com/CodeRedWiki/LPCXpressoExtDebug

Note that if you are talking about the LPC800-Mini board then I seem to remember that the LED has been connected to one of the debug pins, thus you can't use debug and the LED at the same time. And if you have code that is using the LED programmed into the flash, you will need to boot the board into ISP mode before trying to start a debug connection to it.

Regards,
CodeRedSupport

lpcware · ‎06-15-2016

Content originally posted in LPCWare by leon_heller on Fri Jun 21 05:58:50 MST 2013
Rowley CrossWorks works OK with it using the CrossConnect JTAG unit for debugging, so it should be OK with the LPC Link.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by R2D2 on Fri Jun 21 02:44:38 MST 2013

Quote: js-nxp
Am I correct in saying that I can use the LPC link which comes with the LPC1114 board?

Yes.

Quote: js-nxp
This would mean separating the 2 boards (LPC link and LPC1114) and fitting them with connectors for future use and then use J5 connected to J1 of the LPC810 board, correct?

Yes. Or you just try a LPC-Link2. That's better (and no, I don't sell them...).