topic Re: Seventeen different error messages - is this a record? in LPCXpresso IDE

Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:24 GMT

Content originally posted in LPCWare by IanB on Tue Dec 23 13:40:49 MST 2014
Can anyone beat 17 different error messages when trying to get the LPC Link to communicate with a recalcitrant project?

Does anyone have any idea what the problem might have been?

Here they all are:

02: Failed on connect
Invalid emulator index - get list of available emulators.
31: No connection to emulator device

Flash driver "Uninit" return code: 0x0

15: Target error from Commit Flash write
Cannot halt processor
15: Target error from Read register
Cannot access core regs when target running
(crt_emu_lpc11_13_nxp) terminating on communication loss: Pipe has been closed by GDB.

02: Failed on connect
invalid ID for processor
Emu(0) Conn&Reset Was: None, DpID: BB11477. Info: LPCLINK

02: Failed on connect
MEM-AP is not selected
Emu(0) Conn&Reset Was: None, DpID: BB11477. Info: LPCLINK

(crt_emu_lpc11_13_nxp) terminating on communication loss: Pipe has been closed by GDB.

15: Target error from Commit Flash Write
Cannot complete transaction, even after slowing speed
15: Target error from Set break/watch
Unable to set an execution break - no resource available.

15: Target error from Commit Flash write
Cannot halt processor
(crt_emu_lpc11_13_nxp) terminating on communication loss: Pipe has been closed by GDB.

11: Target error from Reset: (null)
15: target error from Register access
Cannot complete transaction, even after slowing speed

Terminate/Disconnect All is not enabled
Reason:
Terminate/Disconnect All is not enabled
To terminate debug sessions, first select a debug session in the Debug View and then select Terminate again

10: Could not start execution from stop
Cannot complete transaction, even after slowing speed

(crt_emu_lpc11_13_nxp) terminating due to loss of debug control

15: Target error from Write register
Cannot complete transaction, even after slowing speed
15: Target error from Set break/watch
Unable to set an execution break - no resource available.

16: Target error from status-Poll
Bad ACK returned from status - wire error.

Failed to execute MU command:
-break-insert -t -f main
Error message from debugger back end:
Could not fetch register "xpsr"; remote failure reply 'E22'
Could not fetch register "xpsr"; remote failure reply 'E22'

Error from StubRegisterDisplayCoreAll: -interpreter-exec console "mon register_display_core
at com.crt.dsfdebug.dsf.commands.MIStubCommandBase.getResult(unknown source)
at com.crt.dsfdebug.dsf.commands.MIStubCommandWrapper.getResult(Unknown Source)
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.process
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run

'Interrupt monitor job' has encountered a proble,
An internal error occurred during "Interrupt monitor job".

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:25 GMT

Content originally posted in LPCWare by lpcxpresso-support on Wed Dec 24 02:36:46 MST 2014
Looks like your target debug circuit is faulty. From the variability of error messages, I'd guess floating or unterminated signals.

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

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:25 GMT

Content originally posted in LPCWare by IanB on Wed Jan 14 07:11:53 MST 2015
According to the manual (UM10398, table 418) the SWDIO and SWCLK pins have internal pullUPs.
Lots of information on the fora suggest that SWCLK should have an external pullDOWN connected. This would bias it at half voltage and make it prone to noise pickup.

I bought a LPCLINK2, and now get these two error messages (and the "help" on them)

Perhaps the problem may be due to the lack of documentation of the LPCLINK2 - I have completely failed to find any pinout for J6, which looks as though it should replace J4 of the original LPCLINK but has a different number of pins

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:26 GMT

Content originally posted in LPCWare by lpcxpresso-support on Wed Jan 14 07:16:30 MST 2015
You should use J7. J6 is for ETM, which is not used.

Please follow the debug design guidelines here:
http://www.lpcware.com/content/faq/lpcxpresso/debug-design

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:27 GMT

Content originally posted in LPCWare by R2D2 on Wed Jan 14 07:32:26 MST 2015

Quote: IanB
Perhaps the problem may be due to the lack of documentation of the LPCLINK2 - I have completely failed to find any pinout for J6, which looks as though it should replace J4 of the original LPCLINK

What's wrong with:

http://www.embeddedartists.com/sites/default/files/support/xpr/link2/LPC-Link-II_Rev_C.pdf

And yes, J6 can be used to connect your target and it's replacing J4 of LPC-link :)

There are several LPC-links available (with 8 or 9 pins) :O

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:27 GMT

Content originally posted in LPCWare by IanB on Wed Jan 14 08:29:52 MST 2015

Quote:
What's wrong with:

http://www.embeddedartists.com/sites/default/files/support/xpr/link2/LPC-Link-II_Rev_C.pdf

Well, quite a lot really, like having to search through 6 pages of circuit diagram to find a pinout.

How about a manual, perhaps, which lists the connectors and their pinouts?

Anyway, problem seems to be with Vio_buf_b which collapses when the probe tries to transmit.
Reason as yet unknown.

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:28 GMT

Content originally posted in LPCWare by R2D2 on Wed Jan 14 08:37:39 MST 2015
Did you read #5 of:

http://www.lpcware.com/content/forum/lpcxpressolpc114fn28102-questions

Quote:
[color=#f00][u]J2 Confusion:[/u][/color]

J2 is also used to supply VIO_BUF_B. With simple boards (simple SWD connection) this jumper has to be closed, or R38 (1k) has to be added...

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:28 GMT

Content originally posted in LPCWare by TheFallGuy on Wed Jan 14 08:55:15 MST 2015
The pinouts are a standard and they are shown in the FAQ:
http://www.lpcware.com/content/faq/lpcxpresso/debug-design

On LPC-Link2,
J7 is the "Cortex 10-pin 0.05" JTAG/SWD Connector Pinout"
J6 is the "Cortex 20-pin 0.05" JTAG/SWD/ETM Connector Pinout"

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:29 GMT

Content originally posted in LPCWare by R2D2 on Wed Jan 14 09:03:36 MST 2015

Quote: TheFallGuy
J6 is the "Cortex 20-pin 0.05" JTAG/SWD/ETM Connector Pinout"

Schematic in link above shows:

[color=#f00]J8[/color] is the "Cortex 20-pin 0.05" JTAG/SWD/ETM Connector Pinout

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:30 GMT

Content originally posted in LPCWare by IanB on Wed Jan 14 13:33:09 MST 2015
This is the J6 I'm talking about - according to the circuit diagram SWDIO/SWCLK/RESET/VSS are brought out on pins 2, 3, 6 and 8 - seems like the ideal connector to use. (if I used J7 and its ribbon cable the connector on my target side would be on the trackside, UNDERNEATH the board, which means that the board would have to be removed from the product for programming)

Thanks for the link to "J2 confusion" - that explains a lot! I also note that in #7 of lpcxpressolpc114fn28102-questions LabRat says that pull-ups were found to be unnecessary.

Everyone keeps pointing me to the "Design Considerations for Debug" even though they are obviously fallacious.
Why should I connect a pull-up to SWDIO when it already has one?
Why should I connect a pull-down to SWCLK when it will bias the input to half-supply and make it MORE prone to noise pickup, AND make the input circuit draw supply current?

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:30 GMT

Content originally posted in LPCWare by R2D2 on Wed Jan 14 13:59:54 MST 2015

Quote: IanB
This is the J6 I'm talking about - according to the circuit diagram SWDIO/SWCLK/RESET/VSS are brought out on pins 2, 3, 6 and 8 - seems like the ideal connector to use.

... that's what we are using since 2009, minimal SWD connection :D

With closed J2 and pull-ups for Reset / ISP_0 / ISP_1 LPC-link2 is working with all our LPC1xxx boards...

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:31 GMT

Content originally posted in LPCWare by IanB on Wed Jan 14 14:34:36 MST 2015
Just out of curiosity, R2D2 - what connector do you put on the other end of those wires?
And how long are the wires?

The ribbon cables that are supplied for J7 are just too short - I need enough cable to make sure that the LPClink board is far enough away from any power supply on my pcb, especially the mains side!

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:31 GMT

Content originally posted in LPCWare by R2D2 on Wed Jan 14 15:04:15 MST 2015

Quote: IanB
...what connector do you put on the other end of those wires?

My favorite SWD board connector is a 0.1" 4-pin SMD :)

[img]http://www.lpcware.com/system/files/Board.JPG[/img]

But we also use 0.05"...

Quote: IanB
And how long are the wires?

[img]http://www.lpcware.com/system/files/Connector.JPG[/img]

About 45-50cm :O

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:32 GMT

Content originally posted in LPCWare by IanB on Mon Jan 19 05:17:19 MST 2015
Thanks for that information. I started with the simple 4-way pin header, but found that it came off too easily, and my colleagues were experts at connecting it the wrong way round.

I decided to do some more investigation on the SWD connection.

I got my target board working, using a very short cable (150mm), and changed the pull-ups and pull-downs.
Without any resistors, I get either "no-ACK from Serial Wire" or "target marked as not debuggable"
A stiff pull-up (1k) on SWCLK improves things, but a 1k pull-down leads to the no-ACK error.
This was a little bit of a surprise as SWCLK is mono-directional and driven all the time from the probe.

A stiff pull-up on SWDIO to keep it at V+ during the "turnaround" times would seem like a good idea, but makes little difference.

Adding a terminator (as per lpcxpresso-support, in #1 above) cleared up the overshoot and ringing nicely, but stopped the system working and led to either the no-ACK or the "target marked as not debuggable" error. The terminator was 330Ω in series with 100pF connected from SWCLK to ground (as in Fairchild application note AN-393 "Transmission line effects on High Speed CMOS")

Increasing the wire length to 1m and I was back with the no-ACK error.

An oscilloscope probe on SWCLK often improves things, though I don't see how 10MΩ in parallel with 4pF could possibly make any difference.

So LPCXPRESSO-SUPPORT, let's have your comments; and you still haven't said why SWCLK should have a pull-DOWN - even your own website
http://www.lpcware.com/content/blog/introduction-cortex-serial-wire-debugging-part-one
says that the signal is at V+ when inactive.

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:33 GMT

Content originally posted in LPCWare by lpcxpresso-support on Mon Jan 19 07:58:49 MST 2015

Quote:
even your own website
http://www.lpcware.com/content/blog/introduction-cortex-serial-wire-debugging-part-one
says that the signal is at V+ when inactive.

That was written by a user and not NXP...

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:33 GMT

Content originally posted in LPCWare by IanB on Mon Jan 19 09:04:07 MST 2015

Quote:
That was written by a user and not NXP...

Is it wrong? My 'scope would say he's correct.

. . . and I'm still hoping for the official explanation of the pull-ups/pull-downs.

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:34 GMT

Content originally posted in LPCWare by lpcxpresso-support on Tue Jan 20 02:35:00 MST 2015
From our board designer:

[list=1]
[*]The Link2 SWD, JTAG & parallel trace interfaces are all buffered using dual power supply buffers. The Target side of the buffer is typically powered from the Target VREF when interfacing through J7 or J8.
[*]J6 on the Link2 board can be used for the SWD interface as long as the VIO_BUF_B is properly powered. As long as the Target VDDIO is between 2.7 – 3.3V, the easiest way to do this is to shunt JP2 (see below). A zero ohm resistor can also be installed at R38.

[img]http://www.lpcware.com/system/files/image002.png[/img]
[*]The SWD interface is designed to be point to point. That means on the Link2 board only one SWD interface should be connected. When J6 is used, do not have any cables installed at J7 or J8. The same is true on the Target board, so from the SWD connector on the Target board there should be minimal trace stubs branching off the SWDIO and SWCLK signals to the Target MCU.
[*]When using J7 and J8, the 50 mil pitch ribbon cable with the adjacent gnd wire to SWDIO and SWCLK has approximately a 100ohm characteristic impedance. On the Link2 board the series terminators (R17 & R18) near U3 driver chip matches this cable impedance. When buffer U3 drives SWDIO and SWCLK towards the Target the signal sent down the cable is only half the size output by the buffer, but due to a high impedance at the Target end of the cable the signal doubles to full voltage at the Target MCU. The half size signal reflected back to the source is terminated by the R17 & R18 on the Link2 board. When SWDIO is driven by the NXP LPCxxxx Target MCU, the buffer in the MCU has slew rate control and an internal impedance that matches 60 to 100 ohm cable pretty well and so no additional series termination is typically needed at the Target MCU.
[*]When using J6 on the Link2 board with fly wires, especially longer ones like you want to use, it will likely help to use a twisted pair for SWDIO and SWCLK. Both gnd wires can terminate in to J6-8 on the Link2 board and at gnd on the Target board.
[*]The long wires you are using will add more capacitance load to the buffer output. Requiring more power from the buffer to charge / discharge the wire capacitance. If the Target VDDIO is between 2.7 – 3.3V another possible help is to short SJ1 2-3 (use 0Ω resistor or solder ball). The resistor between SJ1 1-2 doesn’t need to be removed. This will eliminate the D4 diode from causing some droop on VIO_BUF_B. The shunt is still required at JP2.
[img]http://www.lpcware.com/system/files/image004.jpg[/img]
[*]Not all LPCxxxx chips have an internal pullup or pulldown on the SWCLK pin. For the chips that do have a pull-up on SWCLK, I suggest using a 10k pullup on the Target board. If the chip has a pull-up on SWCLK, I would not put a pull-down on the board. That puts the dc level near the input threshold when the clock is not being driven and this is not recommended.
[/list]

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:35 GMT

Content originally posted in LPCWare by IanB on Tue Jan 20 14:09:14 MST 2015
That's really helpful, and makes sense of it. It's exactly what I thought about pull-downs on SWCLK.

I used telephone cable with two twisted pairs (Z=110Ω) - SWCLK and GND on one and SWDIO and RESET on the other, with 100nF between reset and ground to stop the crosstalk resetting the device. Does it ever use reset? I've never seen any waveform on it.

I still find the interface extraordinarily sensitive to cable length and very small amounts of extra capacitance:
15pF on SWCLK was enough to stop it working. That's adding a delay of only 2 ns. At 3MHz, I would have expected to withstand extra delays of in the order of 100ns before it stopped working.

If I were a betting man, I would wager that the data was being sampled on the wrong edge of the clock.

Microchip uses a similar two-wire interface, and I seem to remember its being a lot more robust (although it did run at a considerably lower speed)

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:36 GMT

Content originally posted in LPCWare by R2D2 on Tue Jan 20 14:28:36 MST 2015

Quote: IanB
Does it ever use reset? I've never seen any waveform on it.

Which MCU are you using? My LPC11Cxx boards don't use Reset :)

Re: Seventeen different error messages - is this a record?

lpcware — Thu, 16 Jun 2016 01:34:36 GMT

Content originally posted in LPCWare by IanB on Tue Jan 20 14:59:48 MST 2015

Quote:
Which MCU are you using?

LPC1111, LPC1113 and LPC1224 - It says that it needs to be connected but when I monitor it with a scope, I've never seen anything happen.