Hello Team
May I ask about ENEDC of K3?
Customer uses MCAL with RTD.
However, I did not find the information of RTD about ENEDC.
from MSCM, it is showing only ISR core assign configuration.
May I ask, how to enable ENEDC using RTD(MCAL)?
Thank you.
Hi @Luke_Chun ,
as per my understanding from RM description, it is needed to enable these bits if you want to have report path form the gaskets to FCCU active.
This is why sCheck is enabling these bits otherwise it would be not possible to test the report path.
I have to agree that this is essential setup and maybe a lot of K3 customers are not even aware of this setup (just enabling related FCCU channel, but not these bits).
Kind Regards,
Radoslav
Hello @RadoslavB
Thanks for your explanation, but I’m not sure about the ENEDC’s proposal.
Could you confirm my understanding?
Does ENEDC need to use only “TEST”?
Or
Is it need to enable for Safety application? (such as, if User wishes to use the check of eDMA Read, ENEDC’s bit2 will be “set” by manually with FCCU configuration.)
Thank you.
Hi @Luke_Chun ,
there is no request for configuring MSCM peripheral registers in SAF.
The sCheck tests internally enables these registers when it is testing latent faults in associated EDC gaskets, but enabling those bits for application is not covered by any NXP SW.
Therefore, customer shall enable these registers manually.
For S32K5 there has been defined sBoot check for enablement these registers but again, AFAIK configuration is not in scope of any NXP SW.
Kind Regards,
Radoslav
Hi @Luke_Chun,
I don't support issues related to Safety driver. To request support from them, you should remove "RTD" label and keep only "Safety_SW" label in your post. Or you can raise a new post only for Safety_SW.
Best regards,
Dan
Thanks for your update.
I also checked Safety drive but I did not find which one is related with ENEDC...
May I ask, how to check about it?
Thank you.
Hi @Luke_Chun,
RTD driver is not supported for configurating ENEDC. From my point of view, you should check this feature in modules of Safety driver because this register is related to FCCU.
Best regards,
Dan
Adding snippet from K3 HW Safety Manual:
So right now it is up to customer to follow this AoU - configuration and check is not supported by NXP at the moment.
Kind Regards,
Radoslav
Hi @Luke_Chun ,
there is support for configuration of the INTM peripheral, you can find it in RTD Platform plugin - Interrupt Monitors.
On SAF side, sCheck does have INTM latent faults test, but sBoot is not checking any INTM configuration register. In my opinion if Interrupt is as detection/reaction mechanism for safety related fault, then SM1.INT_MON must be active and customer shall fulfill SM4.INT_CHK, sBoot should double check such a configuration.
Kind Regards,
Radoslav
Hi @RadoslavB
may I ask one more question?
How about the INTM_MM?
Is this same with ENEDC?
(RTD or SAF does not support for configuration INTM_MM enable. User has to do the configuration INTM_MM by user code.)
Thank you.