SBC FS26 FS0B and RSTB

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

SBC FS26 FS0B and RSTB

402 Views
kjy106906
Contributor IV

While taking the SBC Test, a question arose.
When I set the SBC as shown below and stopped WD Refresh, I expected that only FS0B would drop to Low, but both FS0B and RSTB dropped to Low.
Can you tell me what causes RSTB to drop to low?
(For reference, in the settings below
When changing from SBC_FS26_FS_WD_FS_REACTION_FS0B to SBC_FS26_FS_WD_FS_REACTION_NO_EFFECT, RSTB does not drop to Low.)

 

static Sbc_fs26_InitConfigType sbcInitConfig =
{
/* FS_I_OVUV_SAFE_REACTION1 register */
{
SBC_FS26_FS_VMON_PRE_OV_FS_REACTION_NO_EFFECT,
SBC_FS26_FS_VMON_PRE_UV_FS_REACTION_NO_EFFECT,
SBC_FS26_FS_VMON_CORE_OV_FS_REACTION_NO_EFFECT,
SBC_FS26_FS_VMON_CORE_UV_FS_REACTION_NO_EFFECT,
SBC_FS26_FS_VMON_LDO1_OV_FS_REACTION_NO_EFFECT,
SBC_FS26_FS_VMON_LDO1_UV_FS_REACTION_NO_EFFECT,
SBC_FS26_FS_VMON_LDO2_OV_FS_REACTION_NO_EFFECT,
SBC_FS26_FS_VMON_LDO2_UV_FS_REACTION_NO_EFFECT
},
/* FS_I_OVUV_SAFE_REACTION2 register */
{
SBC_FS26_FS_VMON_EXT_OV_FS_REACTION_NO_EFFECT,
SBC_FS26_FS_VMON_EXT_UV_FS_REACTION_NO_EFFECT,
SBC_FS26_FS_VMON_REF_OV_FS_REACTION_NO_EFFECT,
SBC_FS26_FS_VMON_REF_UV_FS_REACTION_NO_EFFECT,
SBC_FS26_FS_VMON_TRK2_OV_FS_REACTION_NO_EFFECT,
SBC_FS26_FS_VMON_TRK2_UV_FS_REACTION_NO_EFFECT,
SBC_FS26_FS_VMON_TRK1_OV_FS_REACTION_NO_EFFECT,
SBC_FS26_FS_VMON_TRK1_UV_FS_REACTION_NO_EFFECT
},


/* FS_I_WD_CFG register */
{
SBC_FS26_FS_WD_ERR_LIMIT_6,
SBC_FS26_FS_WD_RFR_LIMIT_1,
SBC_FS26_FS_WD_FS_REACTION_FS0B
},

/* FS_I_SAFE_INPUTS register */
{
SBC_FS26_FS_FCCU_CFG_NO,
SBC_FS26_FS_FCCU12_FLT_POL_0_1,
SBC_FS26_FS_FCCU1_FLT_POL_LOW,
SBC_FS26_FS_FCCU2_FLT_POL_LOW,
SBC_FS26_FS_FCCU12_FS_REACTION_FS0B,
SBC_FS26_FS_FCCU1_FS_REACTION_FS0B,
SBC_FS26_FS_FCCU2_FS_REACTION_FS0B,
SBC_FS26_FS_WAKE2_LP_POLARITY_LOW,
SBC_FS26_FS_ERRMON_FLT_POLARITY_LOW,
SBC_FS26_FS_ERRMON_ACK_TIME_8MS,
SBC_FS26_FS_ERRMON_FS_REACTION_FS0B,
SBC_FS26_FS_FCCU12_FILT_6US
},
/* FS_I_FSSM register */
{
SBC_FS26_FS_FLT_ERR_CNT_LIMIT_6,
SBC_FS26_FS_FLT_ERR_REACTION_NO_EFFECT,
SBC_FS26_FS_RSTB_DUR_10MS,
SBC_FS26_FS_BACKUP_SAFETY_PATH_FS0B_NO,
SBC_FS26_FS_BACKUP_SAFETY_PATH_FS0B_NO,
SBC_FS26_FS_CLK_MON_DIS_ACTIVE,
SBC_FS26_FS_DIS8S_ENABLED
},

/* FS_WDW_DURATION register */
{
SBC_FS26_FS_WDW_PERIOD_256MS,
SBC_FS26_FS_WDW_DC_31C_68O,
SBC_FS26_FS_WDW_RECOVERY_64MS
}

};

Tags (2)
0 Kudos
3 Replies

390 Views
TomasVaverka
NXP TechSupport
NXP TechSupport

Hi Junyeong,

It is caused by no WD refresh during the 256ms INIT_FS state.

image002.jpg

image003.jpg

Best regards,

Tomas

0 Kudos

380 Views
kjy106906
Contributor IV

@TomasVaverka 

hello

My explanation wasn't enough.
I went through the Init FS state with a normal WD Refresh and stopped WD Refresh after some time in Normal state.
Please check again and then respond.

0 Kudos

370 Views
TomasVaverka
NXP TechSupport
NXP TechSupport

Hi Junyeong,

Please double check what value is assigned to SBC_FS26_FS_WD_FS_REACTION_FS0B.

I would expect 1 and then as you correctly stated the RSTB pin should not be asserted low if WD_ERR_CNT[3:0] = WD_ERR_LIMIT[1:0].

Capture.JPG

Best regards,

Tomas

0 Kudos