Other Parts Discussed in Thread: TPS65381A-Q1
Hello,
in the SafeTI™ Hercules™ Diagnostic Library Release Notes (v 2.4.0) there is the following known issue:
We develop a system in an industrial application which is running for several weeks or even months without restart (which would force ABIST / LBIST). From my point of view there is no possibility to guarantee that the TPS is working properly because it can't be tested anymore without the risk to get a power reset.
1) Do you have any idea for a workaround or an argumentation whether it is still useful in this application? Scott Monroe answered this question like this: "I suspect the test run from the Hercules driver team didn't realize these constraints while they had the WD_RST_EN bit set to 1 and the watchdog failures causes the TPS65381A-Q1 to transition through it's RESET state which pull NRES low and would normally reset the Hercules." Is this the case? Then everything would be clear...
2) While testing the ability of ABIST and LBIST I found the following issue:
In the TPS65381A-Q1 Datasheet it is said that "The SPI registers may be unavailable during a BIST, so no SPI reads or writes should be made while the BIST is running". During ABIST I could not discover this behaviour while asking for ABIST_EN, ABIST_RUN and ABIST_ERR flags. All are set in the right manner. But during LBIST execution the SPI receives 0xFFFF so there is no way to get the LBIST_RUN flag, isn't it? If this is the case how can I be sure that the LBIST was really executed? I could ask for ABIST run also...but this is not a nice solution I guess. If I do not get the LBIST_RUN flag the result in LBIST_ERR is worthless because it is initialized with 0 (no error).
Thank you in advance for the support!
With kind regards,
Helge Pape
