Which functions to use, for mtu based smu alarms to get tracked

[yrun431]

Hi,

I am using Tc37x.

I want my SMU to track MTU alarms all the time. For that I have written the code something like this

  IfxMtu_enableModule();

clear_MTU_MBIST_Errors(IfxMtu_MbistSel mbistSel);

Basically, just enabled the MTU clock and then clear the errors caused due to system reset.

Now which other functions should I write [ from IfxMtu.h] to continuosly track the MTU errors.

I have a few questions:

1] for DAM0 do I need to enable DAM0 module too? [by enabling DAM0_CLC?]

2] If I get any MTU error, will my corresponding smu alarms get set automatically? [ As i need to check if smu alarms are set or not, does it happen auto? or do i have to set "AlarmStatus" after configuring MTU bits?]

3] I can see that FSI_RAM is not used in the enum. So do how should I disable this alarm after system reset?

4] I want to set an alarm status in smu (say alm0[9-11]) and lets say I choose  mbistSel =  IfxMtu_MbistSel_cpu0Dspr.

How to set this MTU alarm ? and the corresponding SMU alarm?

5] and for DMA/gigethernet 

I cleared the mbist 41[DMA] and 82,83[ethermacRx/Tx]. But the smu alarm doesn't set to "low", its still "high".

Thank you!!

[yrun431]

@µC_Wrangler 

Can you please help with this

Thanks

[µC_Wrangler]

1) If you're not using DAM, don't worry about testing DAM0.

2) MTU errors will only set the corresponding alarm if ECCS CENE/UCENE/MENE are set.

3) For the TC37x, LMU and FSI alarms are combined, so I don't recommend disabling the alarm.  Write 0 to MC40_ECCD as recommended in application hint SMU_TC.H012 in the Errata Sheet.

4) My general advice is to avoid injecting low-level failures that result in an SMU alarm.  The LBIST tests all of AURIX logic, so there's no need to test the full alarm path for each safety mechanism.  To test your application's reaction to each alarm, leave the SMU in START state, and then you can simply write to SMU_AGx in the debugger.
After you clear MTU error flags, you still need to clear the alarm within the SMU itself.

[yrun431]

thank you @µC_Wrangler 

In the 

clear_MTU_MBIST_Errors()

   ->  IfxMtu_clearErrorTracking(mbistSel);                    /* Clear the error tracking registers (ETRR)    */

function is called. So do i need to enable the error tracking again, so as to always keep checking for the MTU errors?

[µC_Wrangler]

IfxMtu_clearErrorTracking clears the "alarm occurred" bits in MCi_ECCD.  The alarm enable bits are in MCi_ECCS.  Once the alarm is enabled, you don't need to periodically check for MTU errors, unless you've configured the corresponding SMU alarm reaction to no action.

[yrun431]

Thank you @µC_Wrangler 

Can you please tell me,

how to access pms and hsm regs in smu alarm -> alm9[3,5,15,16,17]. Is it similar to MTU, that we need to enable and check mtu and then smu

or directly can we just check smu?

[µC_Wrangler · Accepted solution]

The PMS registers are easier - no exotic clearing/latches/etc.  But keep in mind that the primary voltage monitors are always active, and you might not need to use the secondary voltage monitoring at all.