cannot connect M7_1 on K322

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

cannot connect M7_1 on K322

Jump to solution
257 Views
Micha4566465
Contributor II

when I create an application project in Design Studio 3.6.x for K322,

I can debug the M7_0 core with my PEmicro and the Debug_FLASH_PNE configuration.

When I try to debug the M7_1 core, I cannot establish a connection to this core.

In console there is an error message:

"Could not connect to semihosting port due to connection timeout. Please check that the correct port number is configured."

The status always is halted at 95%.

At the end there is an error window with message: "error 138".

 

I checked that there are no breaking points at start up for the other core.

I also checked that I am using the 100-pin K322 and I checked the correct clock settings.

I checked that in both mex-files.

 

Can anybody help me please?

Tags (1)
0 Kudos
Reply
1 Solution
208 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hi @Micha4566465,

Debug both cores in Launch Group:

danielmartynek_0-1758096453497.png

 

Let me know if you have questions,

 

BR, Daniel

 

View solution in original post

0 Kudos
Reply
3 Replies
209 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hi @Micha4566465,

Debug both cores in Launch Group:

danielmartynek_0-1758096453497.png

 

Let me know if you have questions,

 

BR, Daniel

 

0 Kudos
Reply
53 Views
Micha4566465
Contributor II
That was the problem.
Thx
0 Kudos
Reply
220 Views
elsie78ash
Contributor I

Debugging the M7_1 core on K322 in Design Studio 3.6.x fails due to a semihosting connection timeout and "error 138." This issue likely stems from a port number misconfiguration or a race condition between the two cores, preventing a successful connection to M7_1. To fix this, ensure the correct semihosting port is set for M7_1 and consider initializing M7_0 in a way that doesn't interfere with the debugger's connection KaiserMemberServices to the second core.

 

0 Kudos
Reply