The device can boot-up from either of the four listed options. The option selected depends on the system use case.
- Option 1: ROM
- The device boots up from one of the ROM pages, the EEPROM
overlay is bypassed, and no I2C transactions are performed after start-up.
- Use this option when both DPLL and APLL settings match a ROM
page.
- Option 2: ROM → EEPROM
- The device boots up from one of the ROM pages, then the EEPROM
settings are loaded to the device and overwrite the XO, APLL, and output driver
configuration.
- Use this option when the desired DPLL settings match a ROM
page but the APLL settings do not. Also, use for free-run mode (APLL only, DPLL
disabled) configurations.
- Option 3: ROM → EEPROM → in-system
programming
- The device boots up from one of the ROM pages, then the EEPROM
settings are loaded to the device and overwrite the XO, APLL, and output driver
configuration. I2C transactions are performed after start-up to update the remaining
registers that are not stored in EEPROM (DPLL, SYSREF, and GPIO).
- Use this option when the desired DPLL and APLL settings do not
match a ROM page.
- Option 4: ROM → in-system programming
- The device boots up from one of the ROM pages, the EEPROM
overlay is bypassed, and I2C transactions are performed to overwrite any undesired
register value initialized by the ROM selection (DPLL, SYSREF, GPIO, XO, APLL, and
output driver).
- Use this option when the EEPROM can not be preprogrammed to
reduce start-up time or when the majority of the registers must be configured
in-system.