LPC1769 Debugger/LPC1850 Target/LPCXpresso Error: Target Marked as Not Debuggable

lpcware · ‎06-15-2016

Content originally posted in LPCWare by janderson on Tue Jun 18 08:55:50 MST 2013
Hello,

I'm attempting to burn some sample code I pulled down from the LPCOpen websire to my Hitex LPC1950EVA-A4 board via the LPC1769 debugger platform, but I keep getting the following error message within LPCXpresso:

[img]http://i.imgur.com/fTaSdC2.jpg[/img]
[img]http://i.imgur.com/xo1aVnB.jpg[/img]

I've seen users with similar issues, but their solutions either involved correcting a solder lead or something unrelated to my issues. These are pre-built evaluation boards I'm working with, not something that I've put together.

Any helpful input is appreciated. Thanks!

lpcware · ‎06-15-2016

Content originally posted in LPCWare by janderson on Tue Jun 25 09:27:04 MST 2013

Quote: TheFallGuy
Broken board?

I think this is what it comes down to. I wish I had another board I could test this on, but I do not.

I'll try a couple more things but at this point, I've exhausted my resources.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by TheFallGuy on Tue Jun 25 09:21:36 MST 2013

Quote: janderson
There is no jumper on the JP17 header.

I went ahead and reinstalled LPCXpresso, re-imported the projects, but I still get the same error. I then tried the Red Suite 5 IDE and I get the same error over there, too.

I'm open to suggestions at this point.

Thanks!

Broken board?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by janderson on Tue Jun 25 08:56:50 MST 2013

Quote: TheFallGuy
What have you done with DBGEN (JP17). It should be removed to enable debug.

There is no jumper on the JP17 header.

I went ahead and reinstalled LPCXpresso, re-imported the projects, but I still get the same error. I then tried the Red Suite 5 IDE and I get the same error over there, too.

I'm open to suggestions at this point.

Thanks!

lpcware · ‎06-15-2016

Content originally posted in LPCWare by TheFallGuy on Tue Jun 25 07:35:13 MST 2013
What have you done with DBGEN (JP17). It should be removed to enable debug.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by janderson on Tue Jun 25 06:24:31 MST 2013

Quote: CodeRedSupport
So the Hitex Quickstart Guide suggests that this jumper should NOT be connected. Connecting it will pull the DBGEN pin to ground, disabling debug.

And certainly we don't have this jumper connected on any of these boards that we have here.

Regards,
CodeRedSupport.

Quote: janderson
Ah, so it looks like I'll need to keep it open (pulled up).

I think it may be important to note that once I configure the BOOT jumpers to run from SPIFI, the display no longer shows an output, indicating I am successfully switching between the two memory locations. Correct me if I'm wrong.

Once again, this is my boot jumper configuration per the following link:

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

[img]http://i.imgur.com/f1tY9NO.jpg[/img]

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Tue Jun 25 01:07:38 MST 2013

Quote: janderson

JP17 is a DBGEN jumper that, I assume, allows you to debug the board. I placed a jumper across the header pin right when we received the board, but does this need a jumper, or need to be open (no jumper)?

So the Hitex Quickstart Guide suggests that this jumper should NOT be connected. Connecting it will pull the DBGEN pin to ground, disabling debug.

And certainly we don't have this jumper connected on any of these boards that we have here.

Regards,
CodeRedSupport.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by R2D2 on Mon Jun 24 15:17:42 MST 2013
FlashMagic Database is including 1850, 1853 and 1857...

lpcware · ‎06-15-2016

Content originally posted in LPCWare by janderson on Mon Jun 24 14:57:10 MST 2013

Quote: R2D2
Usually DBGEN = High is enabling JTAG/SWD :)

Ah, so it looks like I'll need to keep it open (pulled up).

Also - is it possible to flash using this Flash Magic program I keep hearing about? Just for testing purposes, of course...

lpcware · ‎06-15-2016

Content originally posted in LPCWare by R2D2 on Mon Jun 24 14:43:27 MST 2013
Usually DBGEN = High is enabling JTAG/SWD :)

lpcware · ‎06-15-2016

Content originally posted in LPCWare by janderson on Mon Jun 24 14:07:31 MST 2013
There is something I came across that nobody mentioned in this topic yet.

JP17 is a DBGEN jumper that, I assume, allows you to debug the board. I placed a jumper across the header pin right when we received the board, but does this need a jumper, or need to be open (no jumper)?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by janderson on Wed Jun 19 08:57:47 MST 2013

Quote: CodeRedSupport
There are two possibilities:
1. You have blown up your target board
2. You have blown up your LPC-Link

I cannot think of anything else.

p.s. as you keep being told, the memory configuration is completely irrelevant until you can actually debug the chip.

I had the LPC1769 target portion resoldered and successfully debugged the Twinkle example program and it is working as it should - looks like this is an issue with the 1850 board.

Also - I have noticed that the display on the screen on the 1850 board is no longer showing up. The demo software used to display a message and display a message when you pushed buttons, moved the jostick, etc, but no longer shows up. HOWEVER, once I moved the BOOT2 jumped into the 1-2 position, the message comes back. Is this ok?

Thanks.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Wed Jun 19 08:32:53 MST 2013
There are two possibilities:
1. You have blown up your target board
2. You have blown up your LPC-Link

I cannot think of anything else.

p.s. as you keep being told, the memory configuration is completely irrelevant until you can actually debug the chip.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by janderson on Wed Jun 19 08:07:48 MST 2013

Quote: CodeRedSupport
The fundamental problem (as mentioned by thefallguy) is that LPC-Link cannot see your MCU on SWD. Therefore, until you fix this problem, you will not get ANY debug session to work.

So, to find out why the MCU is not found you will need to try all of the things below (which have all been mentioned before, but you seem to be ignoring):
- power to board matches spec given by Hitex. If you are using USB power, then use a powered hub rather than a PC usb socket.
- cable between LPC-Link and board. Any signs of damage? If you have another cable, try using it.
- try using the LPC-Link with another target board. Does that work?
- Triple check the way you have split your LPC-Link from the LPCXpresso board's onboard MCU (for example do you have another target board you can try connecting too?)

Can you also confirm the revision of your Hitex board and also the marking on your LPC1850 silicon?

And as a last desperate measure, trying pressing the reset button in combination with ISP before connecting...

http://support.code-red-tech.com/Cod...ebugAccessChip

Oh, and PLEASE stop posting full resolution images

Quote: CodeRedSupport
- power to board matches spec given by Hitex. If you are using USB power, then use a powered hub rather than a PC usb socket.

Quote: janderson
I've confirmed that I have a capable power supply (wall wart, +5 VDC, 2.5 A).

Quote: CodeRedSupport
- cable between LPC-Link and board. Any signs of damage? If you have another cable, try using it.

Quote: janderson
The cables between the LPC-Link 1769 board, and the Hitex 1850 board is brand new and does not appear to be damaged in any way shape or form.

Tried a second cable - same result.

Quote: CodeRedSupport
- try using the LPC-Link with another target board. Does that work?

We do not have any other target board, these are the only two our NXP rep. delivered to us. When the target portion of the LPC1769 was soldered together, it was functioning as expected.

Quote: CodeRedSupport
- Triple check the way you have split your LPC-Link from the LPCXpresso board's onboard MCU (for example do you have another target board you can try connecting too?)

See previous post - confirmed this with multimeter.

Quote: CodeRedSupport
Can you also confirm the revision of your Hitex board and also the marking on your LPC1850 silicon?

The back of the board reads as follows:

LPC1850EVA-A4
Hitex Development Tools
www.hitex.com
Made in Germany

-----

The stamp on the processor reads:

LPC1850FET256
PFM906.04 18
ESD1148ZRY

Also - do these memory settings/driver look good to you guys?

[img]http://i.imgur.com/d4jILON.jpg[/img]

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Wed Jun 19 07:43:56 MST 2013
The fundamental problem (as mentioned by thefallguy) is that LPC-Link cannot see your MCU on SWD. Therefore, until you fix this problem, you will not get ANY debug session to work.

So, to find out why the MCU is not found you will need to try all of the things below (which have all been mentioned before, but you seem to be ignoring):
- power to board matches spec given by Hitex. If you are using USB power, then use a powered hub rather than a PC usb socket.
- cable between LPC-Link and board. Any signs of damage? If you have another cable, try using it.
- try using the LPC-Link with another target board. Does that work?
- Triple check the way you have split your LPC-Link from the LPCXpresso board's onboard MCU (for example do you have another target board you can try connecting too?)

Can you also confirm the revision of your Hitex board and also the marking on your LPC1850 silicon?

And as a last desperate measure, trying pressing the reset button in combination with ISP before connecting...

http://support.code-red-tech.com/Cod...ebugAccessChip

Oh, and PLEASE stop posting full resolution images

lpcware · ‎06-15-2016

Content originally posted in LPCWare by janderson on Wed Jun 19 07:13:29 MST 2013
I pulled in a similar program (LPC1850A_HitexA4_Twinkle_SPIFI) and it picked up on my LPC Link once I started the debugging process:

[img]http://i.imgur.com/zb4fwNr.jpg[/img]

After this, it continued on and evenentually blew up, once again:

[img]http://i.imgur.com/5mJXasf.jpg[/img]

[img]http://i.imgur.com/kOpSW9V.jpg[/img]

I've confirmed that I have a capable power supply (wall wart, +5 VDC, 2.5 A).

The cables between the LPC-Link 1769 board, and the Hitex 1850 board is brand new and does not appear to be damaged in any way shape or form.

[img]http://i.imgur.com/uhSHBz9.jpg[/img]

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Wed Jun 19 00:48:23 MST 2013
I presume you've already looked at the FAQ...
http://support.code-red-tech.com/CodeRedWiki/MarkedNotDebuggable

Anyway, I've just tested connection to a Hitex LPC1850 rev A4 board here via LPC-Link using LPCXpresso 5.2.4 (on Win7/64 bit). Board configured for booting from SPIFI flash. Using the LPC1850A_HitexA4_LedBlinky_SPIFI example provided in the LPCXpresso install Examples directory.

No problems seen with connection at all.

So suggest you check
- power to board matches spec given by Hitex. If you are using USB power, then use a powered hub rather than a PC usb socket.
- cable between LPC-Link and board. Any signs of damage? If you have another cable, try using it.
- Triple check the way you have split your LPC-Link from the LPCXpresso board's onboard MCU (for example do you have another target board you can try connecting too?)

Can you also confirm the revision of your Hitex board and also the marking on your LPC1850 silicon?

And as a last desperate measure, trying pressing the reset button in combination with ISP before connecting...

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

Regards,
CodeRedSupport

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Martin84 on Tue Jun 18 15:18:54 MST 2013
I had the same problem but I powered the board with wrong voltage (9V). The problem with the hitex board is, that there's no fuse or voltage regulator which protects against a small overvoltage. You can try to use flash magic and the uart boot mode.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by janderson on Tue Jun 18 12:37:38 MST 2013

Quote: TheFallGuy
As I said in an earlier post, this error is because the debugger cannot see any processor on the end of the SWD/JTAG. I strongly suggest you go an double check that you actually correctly cut the J4 connectors as suggested by R2D2. And then check again. And again...

I have ensured this connection has been cut by using a multimeter to check the connections - I am still receiving the same error.

[img]http://i.imgur.com/aXfxTn2.jpg[/img]

lpcware · ‎06-15-2016

Content originally posted in LPCWare by TheFallGuy on Tue Jun 18 12:18:29 MST 2013
As I said in an earlier post, this error is because the debugger cannot see any processor on the end of the SWD/JTAG. I strongly suggest you go an double check that you actually correctly cut the J4 connectors as suggested by R2D2. And then check again. And again...

lpcware · ‎06-15-2016

Content originally posted in LPCWare by janderson on Tue Jun 18 11:58:40 MST 2013
Also - this is the .cfx flash driver I am using for these projects.

[img]http://i.imgur.com/wdtfozL.jpg[/img]