- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
The ERR monitor function is configurable via SPI write to the SYSPCFG1 register normally. The SYSPCFG1 register is type R2.
These settings should be modified during initialization with the protected register unlocking sequence.
Only during runtime, the settings can be read via a read command to the RSYSPCFG1
register, which is type R3.
And normally when error monitor detects fault, it will move device into INIT state.
Following registers will keep their configuration data instead of being
reset to their default according to reset class *R3):
- RSYSPCFG1 (Configuration of Error Monitoring is kept)
- RWDCFG0, RWDCFG1, RFWDCFG, RWWDCFG0 & RWWDCFG1
(Configuration of Window and Functional Watchdog is kept)
- WWDSTAT (Error Counter status of Window Watchdog)
- FWDSTAT0 and FWDSTAT1 (Status of Functional Watchdog)
So, check firstly if you have modified the setting correctly. Then, check if fault occurs on ERR monitor.
BR,
Xiangrui
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Could you provide more details to describe your issue?
BR,
Xiangrui
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
First,thanks for your reply. Let me elaborate on the problem:
1. I turned off WWD and ERR and put 35584 into normal mode.
2.In normal mode, I used the functions: IfxTlf35584_enableRequestErrPinMonitor() and IfxTlf35584_enableRequestErrPinMonitorRecovery() to enable ERR.
By reading register RSYSPCFG1,note The register is configured successfully.
But 35584 went from normal mode to INIT mode.
I don't quite understand.
LH.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
When an ERR monitor faults occurs, the device will move from its present state to the INIT state. It will also perform a soft reset on the ROT pin and place the system in a Safe State by driving the SS1 and SS2 outputs low.
BR,
Xiangrui
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
So I can understand that the input signal received by ERR pin is wrong?
Thanks,
LH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
The ERR monitor function is configurable via SPI write to the SYSPCFG1 register normally. The SYSPCFG1 register is type R2.
These settings should be modified during initialization with the protected register unlocking sequence.
Only during runtime, the settings can be read via a read command to the RSYSPCFG1
register, which is type R3.
And normally when error monitor detects fault, it will move device into INIT state.
Following registers will keep their configuration data instead of being
reset to their default according to reset class *R3):
- RSYSPCFG1 (Configuration of Error Monitoring is kept)
- RWDCFG0, RWDCFG1, RFWDCFG, RWWDCFG0 & RWWDCFG1
(Configuration of Window and Functional Watchdog is kept)
- WWDSTAT (Error Counter status of Window Watchdog)
- FWDSTAT0 and FWDSTAT1 (Status of Functional Watchdog)
So, check firstly if you have modified the setting correctly. Then, check if fault occurs on ERR monitor.
BR,
Xiangrui
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Thank you very much for your reply,I just checked all the configurations and I found that there was no connection between SMU_FSP and ERR hardware, which caused ERR failure.Now I has solved it.
Thank you again.
BR,
LH.