TLF35584: IF.ABIST and IF.MON are both set during single ABIST

Announcements

From sunburn to sun earn – we’ve got the power! Watch our #poweringgreen videos now.

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
enjoyinf
Level 2
Level 2
10 questions asked 5 replies posted 25 sign-ins

Hi experts, 

    After the first single interrupt  or safe state related comparator on the full path and test, IF.ABIST and IF.MON bit are both set. However, ABIST_CTRL0.STATUS = 5, ABIST_SELECTx = 0 and the corresponding bit in the MONSFx register is set , which seems right.

What is the reason for this?

enjoyinf_0-1684224675972.png

enjoyinf_1-1684225234109.png

Thanks

 

  

 

0 Likes
1 Solution

Hi AliAl,

  I found that the reason for the IF.MON is always set was due to the grounding of the STU, which resulted in a persistent Preg UV fault. 

Thanks

View solution in original post

0 Likes
3 Replies
Albab_A
Moderator
Moderator
Moderator
5 likes given 50 solutions authored 100 replies posted

Hello,

Thanks for the query. In order to provide detailed solution, can you please describe the status for MONSFx and values after reading the bits to check which bit is set .

Best Regards,

Albab

0 Likes

Hi AliAl,

  Thanks for your reply. I tested VBAT_OV, and MONSF3 is 0x01h.

  After I block the conditions in the red box in the following figure, all ABIST can pass.

enjoyinf_0-1684231454917.pngenjoyinf_1-1684231472406.png

Thanks

 

0 Likes

Hi AliAl,

  I found that the reason for the IF.MON is always set was due to the grounding of the STU, which resulted in a persistent Preg UV fault. 

Thanks

0 Likes