LPCXpresso 1769 - Cannot Debug / Load FW - Connection Error

lpcware · ‎06-15-2016

Content originally posted in LPCWare by cell85 on Sun Feb 26 13:58:52 MST 2012
Hi,

my name is Sam and I'm from Germany. I bought a LPCXpresso 1769.
(btw: I'm a STM32F103 + Keil user and I want to change to lpcxpresso/nxp)

I installed the newest Version of LPCXpresso (4.20) and trying to follow the getting started manual.
So I imported a bunch of examples like the ADC-Buzzer or Cmsis-Systick.
I changed the MCU settings from 1768 to 1769. Connected the Board to USB and pressed Debug.

Then this happend and failed to Debug:

Error Popup is saying:

[FONT=Arial]Error launching Debug\adc_buzzer.axf
02: Failed on connect: Ep(01). Target marked as not debuggable.:[/FONT]

in Console:
[COLOR=Red]set remotetimout 60000[/COLOR]

Can anyone help me please ?
Is there a Jumper or something that has to be set/switched/removed ?

with regards,
Sam

lpcware · ‎06-15-2016

Content originally posted in LPCWare by cell85 on Tue Feb 28 05:15:49 MST 2012
GUYS:

Ok I got my second Board today and everything just works perfect.

Seems I killed the Board while splitting it in half.

You have to calculate more space into this part :-)

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Ex-Zero on Mon Feb 27 11:33:04 MST 2012

Quote: cell85
Yes thats why I orderd a second board :-)   But how can I check that.

Am I correct that:
Name            ----------Connector(J4) ----- LPC1769 Pin
SWDIO                 ---------2--------                                    3
SWDCLK             ------3--------                                    5
SWO                     ------------4--------                                    1
RST_N                 ----------5-------                                     17
TDI                      --------------6-------                                      2

// Ok I wait until the new LPCXpresso 1769 arrives. should be tomorrow.

It's not necessary to connect all this wires for SWD :)

#1 LPCXpresso isn't using SWO :(

#2 LPC-Link SWD Connection:

Link__LPC1769__Function
J4-3__Pin 3______SWDIO -Blue
J4-5__Pin 5______SWDCLK -Yellow
J4-11_Pin 17_____Reset -Orange
J4-15___________GND-Black

Picture: http://flic.kr/p/9eJn73

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Mon Feb 27 11:07:18 MST 2012
To connect debug, the LPCXpresso debugger must power up, or enable debug. The "... marked as not debuggable" error is an indication debug did not enable.

I see nothing fundamentally wrong with your test fixture connecting the separated LPCXpresso and LPC-Link boards. It's doubtful you have a pin mapping problem, since the fixture enforces the original mapping. It's hard to tell from the picture, but is it possible you have a cold solder joint? Increase the heat on your solder iron, and try to reflow the J4 connections.

Regards,

CodeRedSupport

lpcware · ‎06-15-2016

Content originally posted in LPCWare by cell85 on Mon Feb 27 03:54:05 MST 2012

Quote: TheFallGuy
You have almost certainly broken something when you split the board. Check all the power AND debug signals.

Yes thats why I orderd a second board :-)   But how can I check that.

Am I correct that:
Name            ----------Connector(J4) ----- LPC1769 Pin
SWDIO                 ---------2--------                                    3
SWDCLK             ------3--------                                    5
SWO                     ------------4--------                                    1
RST_N                 ----------5-------                                     17
TDI                      --------------6-------                                      2

// Ok I wait until the new LPCXpresso 1769 arrives. should be tomorrow.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by TheFallGuy on Mon Feb 27 03:42:57 MST 2012
You have almost certainly broken something when you split the board. Check all the power AND debug signals.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by cell85 on Mon Feb 27 03:40:56 MST 2012
Hi Anders,

thank you for you support.

Yes, the Device is shown up as "USB Device with DFU Capabilities".
Driverversion 3.12.0 , Philips (NXP)

I really would to check the connection from the Bridgepins (J4) to the LPC1769 but I don't now where.

Mybe a Pinout/Via is broken while I cutted it in half but i really took care while cutting.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by andersrosvall on Mon Feb 27 03:32:32 MST 2012
Hi,
I'm Anders Rosvall from Embedded Artists - the company that produces the LPCXpresso boards.
To our knowledge there are no production problems or quality issues with the boards. We have not had a single return because of this. All boards are tested (including flashing) before shipment.

It is our experience that most problems are USB driver related.

If you have problems, please contact our support. Be as specific as possible. We might direct you to Code Reds support if we think it is more likely an USB driver issue.

One thing to check is if the LPCXpresso board show up as a DFU USB device in the Device Handler. This is a good start.

BR,
Anders Rosvall
Embedded Artists AB

lpcware · ‎06-15-2016

Content originally posted in LPCWare by cell85 on Mon Feb 27 03:29:14 MST 2012
@coderedsupport

I'm just using the lpcxpresso 1769.
I separated them as you can see in the picture.

Are they any control-pins / vias? Maybe the Board is faulty or the connector has a faulty connection to the mcu pin.

The Power should be ok, because the blinky-example which is factory-default is running on the 1769 board.

[ATTACH]677[/ATTACH]

/edit:
Vdd = 3,15V
Vext = 4,45V

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Mon Feb 27 03:25:38 MST 2012
I'm not sure which example projects you have imported, but one thing I would suggest is to import the examples from "LPCXpresso176x_cmsis2.zip" into a fresh workspace and see if these project succesfully build and debug.

[To create a fresh workspace - just use [FONT=Courier New][SIZE=2]File -> Switch workspace[/SIZE][/FONT], and select a completely new directory name.]

Let us know how you get on.

Regards,
CodeRedSupport

lpcware · ‎06-15-2016

Content originally posted in LPCWare by serge on Mon Feb 27 02:32:54 MST 2012
For CodeRed and NXP: We are seeing a lot of new threads concerning LPCxpresso 1769 boards not being able to debug.:eek: Maybe it is the right time to check those new boards to see if nothing is wrong with them? :rolleyes:

I am using such a board for some time and will need another one very shortly. Of course i'll wait till the new boards will be shipped fully functioning.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Mon Feb 27 01:14:24 MST 2012
This error is normally caused if the chip is not (properly) powered.

Which board(s) are you trying to debug?
Do you have just an LPCXpresso board, or is it also plugged into an expansion board (baseboard)? If so, make sure the baseboard is powered.
Are you using are 3rd party board? Which one?
Are you using a custom board?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by cell85 on Sun Feb 26 15:06:49 MST 2012
now I'm done watching the videos.... I allready known that whats included in this video.

But my question wasn't answerd with this video.

[B]02: Failed on connect: Ep(01). Target marked as not debuggable.
Emu(0): Connected. Was: None. DpID: EDB6. Info: T1S6RGRIA

[/B]=> http://support.code-red-tech.com/CodeRedWiki/DebugAccessChip

What this means? In the getting Started Video, the guy just plugged in the lpcxpresso and not grounded any pin.

Is this right?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by cell85 on Sun Feb 26 14:14:38 MST 2012
Good Idea!

lpcware · ‎06-15-2016

Content originally posted in LPCWare by NXP_Europe on Sun Feb 26 14:11:33 MST 2012
Hello cell85,

first use 2 hours to look at the introducing videos.

see:
http://ics.nxp.com/support/training/lpcxpresso.intro.1/

and

http://ics.nxp.com/support/training/lpcxpresso.intro.2/