SLVAFL1 October   2024 TPS25751 , TPS26750

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2EEPROM Boot Flow
    1. 2.1 Boot Process
    2. 2.2 Updating the EEPROM Image
    3. 2.3 Commands
    4. 2.4 EEPROM Update Example
  6. 3Source Code Example
    1. 3.1 UpdateRegionOfEeprom()
    2. 3.2 UpdateRegionOfEeprom_Step1
    3. 3.3 UpdateRegionOfEeprom_Step2()
    4. 3.4 UpdatingRegionOfEeprom_Step3()
    5. 3.5 UpdatingRegionOfEeprom_Step4()
    6. 3.6 WriteRegionPointer()
  7. 4Recovering From EEPROM Failure
  8. 5Summary
  9. 6References

4 Recovering From EEPROM Failure

If the EEPROM loading terminates without a valid Patch Bundle, then the INT_EVENTx.ReadyForPatch interrupt gets asserted. The host must read the BOOT_STATUS register 0x2D to discover why booting from EEPROM failed. Then the host must force the PD controller into the APP mode by pushing a patch using the PBMx commands (see Technical Reference Manual for details). This can be the full Patch Bundle that is normally in EEPROM. After the PD controller is in the APP mode, the host can write to the EEPROM using the FLxx commands and correct the problem. Figure 4-1 shows the recommended boot flow.

This boot flow requires the host to be able to correct the EEPROM. If the host requires the PD controller to enable the sink path before it can boot, then the appropriate dead-battery configuration must be selected by the ADCINx pins. In this case, the SafeMode dead-battery configuration is not applicable.

Recommended Boot Flow for EEPROMFigure 4-1 Recommended Boot Flow for EEPROM