FS85xx: Behaviour when trying to close INIT_FS with a wrong WD

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

FS85xx: Behaviour when trying to close INIT_FS with a wrong WD

ソリューションへジャンプ
993件の閲覧回数
AndreasStolze
Contributor IV

Hi all,

quick question: What happens, if the challenger WD is used, and a bad WD is sent during trying to close the FS_INIT?

AndreasStolze_0-1712311440174.png

There's the WD_ERR_LIMIT, but is it also applied here?

Currently we're seeing a direct assertion of the RSTB pin but want this to be confirmed.

Also regarding debug mode:

Would be behaviour here be identical? Also a instant reset when the wrong WD is sent?

AndreasStolze_1-1712311600182.png

 

Thank you
Andreas

0 件の賞賛
返信
1 解決策
976件の閲覧回数
TomasVaverka
NXP TechSupport
NXP TechSupport

Hi Andreas,

Yes, if there is no WD refresh or a bad WD refresh is sent during the INIT_FS phase, RSTB pulse is generated, the fault error counter is incremented by 1 and a new initialization phase is automatically started when RSTB is released.

No, in Debug mode, the INIT_FS window is infinite and the WD window is fully opened meaning WD errors are not taken into account.

BR, Tomas

元の投稿で解決策を見る

2 返答(返信)
977件の閲覧回数
TomasVaverka
NXP TechSupport
NXP TechSupport

Hi Andreas,

Yes, if there is no WD refresh or a bad WD refresh is sent during the INIT_FS phase, RSTB pulse is generated, the fault error counter is incremented by 1 and a new initialization phase is automatically started when RSTB is released.

No, in Debug mode, the INIT_FS window is infinite and the WD window is fully opened meaning WD errors are not taken into account.

BR, Tomas

973件の閲覧回数
AndreasStolze
Contributor IV

Thanks! Quick question, quick answer!

0 件の賞賛
返信