Error in final launch sequence

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Error in final launch sequence

1,887 Views
srrp
Contributor I

Hi, 

I'm trying to build and debug an sdk example on my LPC54018. I'm using MCUXpresso IDE v11.3.0_5222 and SDK LCP54018. 

I'm able to import the project, to build the project (which give me zero errors) but when I debug it, it keep showing this error.

image (1).png

0 Kudos
Reply
5 Replies

1,874 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello,

How about debug a simple LED SDK demo?

If still can't work, please enter ISP mode, erase all, then debug again.

About detail refer to:

https://community.nxp.com/t5/LPCXpresso-IDE-FAQs/Regaining-debug-access-to-target-MCU/m-p/473923  

 

BR

Alice

0 Kudos
Reply

1,869 Views
frank_m
Senior Contributor III

I think the Eclipse debug interface is unneccessary difficult and awkward.

Have you started the debuuging properly ?

First, select the debug dropdown menu, as shown in the snapshot.

From the menu, select "Debug as...".

Then, select the proper debug adapter. In your case, probably "MCUXpresso IDE LinkServer (CMSIS-DAP)".

frank_meyer_0-1616745801527.png

 

0 Kudos
Reply

1,853 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

 

Hello Frank,

You can directly choose debug way refer to your debug probe under "Quickstart Panel",

or click "Debug" button and pressing Shift button on your PC, IDE will search the debug probe automatically. 

Alice_Yang_0-1616982584008.png

 

0 Kudos
Reply

1,848 Views
frank_m
Senior Contributor III

If I am remembering correctly - only once you went through the mentioned process, and selected one of the available debug options. I know, this is one of the Eclipse quirks.

Other toolchains do this in a much better and and more comprehensive way. The debug pod is selected during project setup, since it is usually fixed by hardware, and rarely ever changes for a project. You just press a "debug" button, and the initially assigned adapter is assumed. E.g. with IAR WB, Keil uVision, and Rowley Crossworks.

0 Kudos
Reply

1,839 Views
converse
Senior Contributor V

There is a preference (Window->Preferences) to select which probes to 'discover'. If you don't have (for example) a J-Link or a P&E probe, just uncheck them from the list - see screenshot below

Screenshot 2021-03-29 at 14.23.38.png

Next time you start a debug session with a new project, it will only look for those that are checked.

Note that once a debug probe is selected for a Debug configuration, the probe persists, so it is a one-time selection.

0 Kudos
Reply