Question of MPC5676R core 1 stop issue

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

Question of MPC5676R core 1 stop issue

Jump to solution
843 Views
Luke_Chun
NXP Employee
NXP Employee

Hello Team

 

Could you check the abnormal phenomenon of MPC5676R?

MPC5676R is used both core 0 and core 1.


The issue is that Core 1 is stopped, almost(Easy duplication…just power on, it can make duplication.) and could not implement application code by core 1.(core 0 is working well, always)
Sometimes, Core 1 is working well but it is stopped after few min or sec. After Core 1 stop, it cannot re-work by any ways....just try to re-power on...

 


My investigation is below;


1. It can make same issue(core1 stop) if S/W is used the reference code(Core1 is stopped using other S/W.)
And it is working well if other MCU is downloaded by the dump flash data from issue MCU.
So I think that the application S/W is not the reason…

 


2. When I use the T32 for debug, Core 1 is showing entry point or reset state(could not access J-tag, it is showing "???" or holding values) during issue condition.
When I tried to reset using SIU_RSTVEC1 / RST bit for core 1, it is returned "0" by automatically during issue condition(core 1 stop).
However it keeps “1” during working Core 1 condition. And I changed “RST” bit to “0”, core 1 jumps to entry point and working well.(it is normal working condition...)
So I think that “something” is released reset of core1 during issue condition(core1 stop.)

 


3. when the issue condition(Core 1 stop), Core power consumption is increased...

 

 

Did you see the similar issue? And could you let me know any guidance of this issue?(how to debug, which information can make sure for understanding.)

 


Thank you.

Labels (1)
0 Kudos
1 Solution
721 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi,

just to be sure that my understanding is correct: you can see this issue on single device only and exactly the same software is running without any problems on other board, right?

I have never seen that, so just a few ideas I would try:

- even if it is not related to SW, try to run only simple endless loop on core 1. Don't do anything else. Is this working?

- have you double-checked all clock settings? Is the device operating within specification?

- is it custom design? If the same software is running fine on other board, is that exactly the same design? Is it possible to re-solder the MCU from the board to another one for test purposes?

Regards,

Lukas

View solution in original post

1 Reply
722 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi,

just to be sure that my understanding is correct: you can see this issue on single device only and exactly the same software is running without any problems on other board, right?

I have never seen that, so just a few ideas I would try:

- even if it is not related to SW, try to run only simple endless loop on core 1. Don't do anything else. Is this working?

- have you double-checked all clock settings? Is the device operating within specification?

- is it custom design? If the same software is running fine on other board, is that exactly the same design? Is it possible to re-solder the MCU from the board to another one for test purposes?

Regards,

Lukas