Hi Alice,
I have some questions about FCCU errors resources of MPC5744P. Would you help me?
Yes
First, NCF[7] STCU2 fault condition (run in application mode) , does it means that MCU enter BIST mode unexpectedly? As we know, BIST will be performed when start-up and shun-down. It would not enter BIST mode when MCU is in application mode? How and when will make NCF[7] occur?
Yes, you are right, BIST runs only in starup/shutdown mode. Not during application execution.
NCF[7] indicates that LBIST/MBIST control signals are getting into an unexpected state during application runtime. For example due to cosmic radiation, bit flip, or high magnetic field, etc...
It monitors unexpected behavior of BIST during application runtime.
Secondly, how to clarify the NCF and CF? Does it predefined in DCF records? User cannot change a NCF to a CF?
This is old markings which comes from MPC56xx devices. On MPC57xx devices in FCCu module there are all fault Non Critical (NCF).
It is up to user how he will set up reaction path on particular fault. For example reset or interrupt ALARM.
On MPC56xx devices reaction on CF was always reset. Now we offer user possibility to decide which fault is critical for him and which not.
Thirdly, what's the difference between NCF[8-9] and NCF[60-64]. It seems like that NCF[8-9] contain NCF[60-64] and NCF[60-64] just a part of BIST results. Why specailly list MBIST results in NCF[60-64] while no LBIST results.
The fault 8-9 covers also LBIST results. While 60-64 reports specially selected memory regions which I expect are not rooted to faults 8-9. Actually I have never get MBIST failure from tests. LBIST reports to 8-9.
Another question: what are the differences between NCF[8] BIST results (critical faults) and NCF[9] BIST results (non-critical faults) ? Are there any examples for NCF[8] and NCF[9]?
This comes from STCU older architecture. This is quite complicated to explain here. So shortened there are only NCF even if you can see CF and NCF in FCCU. Both are NCF.
Have a nice day,
Peter