Mar 03, 2021
09:57 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 03, 2021
09:57 AM
Hello,
Some alarms are configured to trigger SMU1 interrupt.
But this interrupt is raised only once. It seams this is caused by the fact that bit IRQ1STS in the AEX register need to be reset.
To reset this bit I need to write the IRQ1CLR bit in AEXCLR register.
But this register is write protected, so I need to remove the END INIT protection.
But whatever I tried I did not managed to clear AEX.IRQ1STS.
I removed the Safety End Init, I tried also by removing the CPU end init.
I tried the MCAL function Smu_ClearAlarmExecutionStatus(), but with no success.
Can you please support me?
Some alarms are configured to trigger SMU1 interrupt.
But this interrupt is raised only once. It seams this is caused by the fact that bit IRQ1STS in the AEX register need to be reset.
To reset this bit I need to write the IRQ1CLR bit in AEXCLR register.
But this register is write protected, so I need to remove the END INIT protection.
But whatever I tried I did not managed to clear AEX.IRQ1STS.
I removed the Safety End Init, I tried also by removing the CPU end init.
I tried the MCAL function Smu_ClearAlarmExecutionStatus(), but with no success.
Can you please support me?
1 Reply
Mar 09, 2021
01:08 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 09, 2021
01:08 PM
Hi dannydc89. AEXCLR is *safety* endinit protected, as specified in Table 539: the "SE" means Safety Endinit.
It could be that you cleared the SMU's IRQ1 flag, but the fault from the underlying hardware mechanism also needs to be cleared.
Which alarm are you getting?
It could be that you cleared the SMU's IRQ1 flag, but the fault from the underlying hardware mechanism also needs to be cleared.
Which alarm are you getting?
This widget could not be displayed.