MPC5748G mutil core debug failed on Trace 32

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

MPC5748G mutil core debug failed on Trace 32

1,125 Views
huqiang
Contributor IV

Hello, 

I was using the AUTOSAR OS (MPC574xG_AUTOSAR_OS_4_0_92_RTM_1_0_3) on MPC5748G.

For the sample "sc1", I have used the command "make core=both debug=yes", and generated files for Lauterbach T32 debug.

My problem is that when I launch the "sample1.bat", I can only connect and debug on core Z4A but failed on core Z2 with "target processor in reset".

2.PNG

1.png

How can I fix this problem?

Sincerely,

Qiang Hu

Tags (3)
4 Replies

882 Views
petervlna
NXP TechSupport
NXP TechSupport

Hi,

I see your core z2 is in reset.

Check mode entry module core status register. ME_CS if core z2 is active.

Peter

882 Views
huqiang
Contributor IV

Hello,

In the MC_ME_CS, the status of core Z2 is disabled.

But I just use sample codes download from the NXP website.

When running, the status of core Z2 is disabled.

How can I enable it?

The attachment is the sample code.

The path is :...\OS\sc1\output\bin\sample1.bat

HU

0 Kudos

882 Views
petervlna
NXP TechSupport
NXP TechSupport

Ok,

So now you know why you cannot connect to z2 core.

Enable it in mode entry module by:

1. Providing z2 start address in CADDR register and set also RMC bit in this register.

2. Define in which mode the z2 will be active in CCTL register.

3. do mode transition to mode where z2 is active.

Now you can connect with no issues.

Peter

PS: if you still struggle check my example code:

https://community.nxp.com/docs/DOC-335369 

882 Views
huqiang
Contributor IV

Hi, Peter

I think the generated AUTOSAR OS application  "sample1.elf" didn't have the related setting about enabling z2.

I will try to find out how to configure this in EB tresos.

Thanks for your help.

Hu

0 Kudos