7.5.41 STATUS_MFR_SPECIFIC (80h)
The STATUS_MFR_SPECIFIC command returns one byte of information relating to the status of manufacturer-specific faults or warnings.
COMMAND |
STATUS_MFR_SPECIFIC |
Format |
Unsigned binary |
Bit Position |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Access |
r/wE |
r |
r |
r/wE |
r |
r |
r |
r |
Function |
otf_bg |
illzero |
illmany1s |
iv_ppv1 |
iv_ppv0 |
0 |
is_Slave |
sync_flt |
Default Value |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
A 1 in any of these bit positions indicates that:
otf_bg The internal temperature from bandgap is above the thermal shutdown (TSD) fault threshold. This bit is writeable to clear and the EEPROM bit is for SMBALERT_MASK.
illzero The operation FSM has hit an illegal ZERO state. The FSM is a one-step implementation, so all zeros in the state is illegal and should never occur. This event is informational only and would not trigger SMBALERT.
illmany1s The operation FSM for has hit an illegal more than one hot state. The FSM is a one-hot implementation, so a state where multiple state bits are HI is illegal and should never occur. This event is informational only and would not trigger SMBALERT.
iv_ppv1The ADDR1 detection fails to resolve 4 consecutive values. To avoid initial turnon events from clearing this condition and the user not being aware why the default ADDR1 value was used, this bit is only clearable through the CLEAR_FAULTS command or writing a logic 1 to this bit, essentially off and on events do not clear it as with the other standard status bits. This condition will trigger SMBALERT.
iv_ppv0 The ADDR0 detection fails.
sync_flt A synchronization fault. This could be because (a) Clock slave: an expected external SYNC was never present; or present, then lost, or (b) Clock master: an internal SYNC signal is not sensed on the SYNC pin. This bit is a live (essentially, unlatched) indicator. This event is informational only and would not trigger SMBALERT. This bit will always read 0 if the DIS_SYNC_FLT bit is set.