TPS65381A-Q1: SPI after reset

Hello Shinichi-san,

All registers are re-initialized by a NPOR event (TPS65381A-Q1 power on reset). STANDBY state if held long enough will cause NPOR indirectly.  Some registers are re-initialized by LBIST running, including when LBIST runs on the transition into DIAGNOSTIC state from RESET state (assuming AUTO_BIST_DIS was not changed from the default of 0). 

During RESET state the SPI communication logic itself is in reset, not the registers. 

Section 5.5.3 SPI Registers (SPI Mapped Response) section of the datasheet lists the registers that are re-initialized by LBIST running. 

In the updated datasheets that just published for both TPS65381A-Q1 and TPS65381-Q1 (Rev G) we added this information to each register in the register map.  Below is one example of this where I have circled the initialization source information.  Additionally with these new versions of the datasheet we have added in each registers map the controller access type (read-only, read write and a note if the write update can only occur in DIAGNOSTIC state).   

Most of the fault (error) status bits are self clearing when the error is gone they will also clear or be re-initialized after STANDBY or RESET state (LBIST).

The configuration registers that are not re-initialized after LBIST are a good way to determine if RESET state occurred or if NPOR occurred.

Best Regards,

Scott