PFE0 ping issue

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

PFE0 ping issue

635 Views
Abhiram_m_s
Contributor I

Hello ,
We are using BSPS 43 on Acore and autosar on Mcore
Acore is using pfe0,pfe1 and pfe2 and Mcore is using gmac

When the A-core is booted alone, PFE0 is able to successfully ping external IPs (e.g., 8.8.8.8). However, during a multicore boot (A-core + M-core), the ping fails.
To investigate this, we placed a breakpoint at the Mcu_InitClock() function in the M-core. Interestingly, when the execution is halted at this point, the A-core is able to ping successfully.
I have attached the screenshot below
 
Abhiram_m_s_2-1750674161322.png

 

However, once the M-core is allowed to proceed beyond this breakpoint, the A-core freezes. As shown in the screenshot below
 
Abhiram_m_s_3-1750674228318.png

 

 

We have also observed that if we introduce a delay of approximately 5 seconds at the beginning of the M-core execution, the A-core is again able to ping successfully.
This further suggests that the issue is likely related to a conflict in clock or peripheral initialization between the cores.
This is not the case with PFE1 and PFE2.  It successfully pings during both multicore and just Acore boot.

Could you let us know what the issue might be?
Tags (1)
0 Kudos
Reply
1 Reply

617 Views
chenyin_h
NXP Employee
NXP Employee

Hello, @Abhiram_m_s 

Thanks for your post.

From the logs described, it is possibly because there is clock conflict existed between M and A core side, I suggest checking your MCU module settings of the M core side to check if PFE0 clock is touched from M core perspective.

 

BR

Chenyin

0 Kudos
Reply