Can't debug LPC55S66JBD64

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

Can't debug LPC55S66JBD64

Jump to solution
2,947 Views
Secad
Contributor II

Hi,

I have a custom board with a LPC55S66JBD64. I am using MCUXpresso v11.5.1 with a J-Link Segger probe.

I succeed to realize the debug authentication following the AN13037:

Debug_autnetication.png

but I can't debug the board with MCUXpresso even if I modify CMPA and CFPA configuration and set PIN/DFLT of DBGEN&SPIDEN to 'Always Enable'. I have tried to debug the "hello world" project without success.

I have the error "Failed to execute MI command". It seems that there is a problem with the GDB server

Is there something to configure on MCUXpresso to make it work?

Cheers.

Cédric

0 Kudos
Reply
1 Solution
2,891 Views
Secad
Contributor II

Hi,

I have bought a new Segger probe (8.08.00 J-LINK BASE) and now it works.

Cédric

View solution in original post

0 Kudos
Reply
8 Replies
2,929 Views
Purcell854
Contributor I

Did you ever find a solution for this? I'm in the same situation. Still getting same error message.  PointClickCare CNA

0 Kudos
Reply
2,926 Views
Secad
Contributor II

Hi,

Actually, I haven't found solution. I'm loading the board trought the ISP interface and I debug with the UART which is particularly annoying...

Cédric

0 Kudos
Reply
2,939 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello, 

 

Does it can debug well before enable  authentication ?

 

BR

Alice

Tags (1)
0 Kudos
Reply
2,936 Views
Secad
Contributor II

Hi Alice,

I don't succeed to debug the board before enable/disable authentication. I have the same error, that's why I have tried the debug authentication.

Is it possible to debug a board with a new component (from NXP) without perform the debug authentication?

You will find bellow the error from MCUXpresso:

Error in final launch sequence: Failed to execute MI command: -target-select remote localhost:2331

Error message from debbugger back end: localhost:2331: Connection timed out

I have check the SWD connection and the reset.

Other question, during debug authentication, the debbugger should communicate with the MCU, so the SWD link should work?

Cheers.

Cédric

 

0 Kudos
Reply
2,932 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello ,

1) Debug authentication is a security method to debug, the prerequisite is that the board can debug well.

2) "Other question, during debug authentication, the debugger should communicate with the MCU, so the SWD link should work?"

->>NO, debugger sends the debug authentication start command to the device through the debug mailbox.

 

BR

Alice

 

0 Kudos
Reply
2,927 Views
Secad
Contributor II

Hi Alice,

I have checked all the board:

- Pull-up on P0_5

- SWD interface: I have check it almost 10 times...

- Power supply: 3.3V is OK, DCDC for VDD_PMU seems to be disable when the board is reset by the probe, otherwise the voltage is good

I have seen this post: https://community.nxp.com/t5/LPC-Microcontrollers/LPC5502-SWD-not-detected/m-p/1276036

Is there prefered probes to bebug the LPC55S66? I have tried PEMicro Multilink Universal, J-Link Segger and LPC-LINK2 without success.

Furthermore, I haven't understand if it's possible to debug without performing the debug authentication?

Cheers.

Cédric

0 Kudos
Reply
2,921 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hello,

I mean before using authentication. Just want to confirm the SWD hardware works well before. 

0 Kudos
Reply
2,892 Views
Secad
Contributor II

Hi,

I have bought a new Segger probe (8.08.00 J-LINK BASE) and now it works.

Cédric

0 Kudos
Reply