Below are some of the features of OTP
CGU Configuration:
CGU configuration is performed using an Init Block in the boot stream. This provides greatest flexibility.
In situations where boot time must be kept to a minimum, settings in the OTP can be applied at this stage of prebot as opposed to during the boot process itself. The settings for the CGU are located within the struct ADI_ROM_OTP_BOOT_CGU_INFO structure. Please refer the Table 40-7: "ADI_ROM_OTP_BOOT_CGU_INFO" in page: 1824.
DMC Initialization:
When a processor is locked, the boot process does not support an Init Block in the boot stream. For a locked processor programs must use the OTP to reconfigure the clocks. And you can initialize DMC peripheral during boot without the use of init codes in the boot stream. ADI_ROM_OTP_DMC_CONFIG provides details of the OTP region that is used to store the DMC configuration. Please refer Table 40-60: "ADI_ROM_OTP_DMC_CONFIG" in page: 1928
Boot Command Customization:
OTP can be also used to customize the Mode peripheral, For example by default SPI2 is the boot peripheral for SPI Master and slave boot. It can be customized to other SPIs also, this allows permanent customization of a particular boot mode. ADI_ROM_OTP_BOOT_CMD_INFO This boot command object for storing a customized boot command for each boot mode within the OTP memory
array. Please refer Table 40-59: ADI_ROM_OTP_BOOT_INFO in page: 1927
Boot Address:
Boot address can be changed using OTP. By default, Boot address is 0th address. Using the OTP, it can be changed to other address within the given range in Datasheet.
For more details on OTP please refer the table "Table 10-3: ADSP-2156x OTP Layout" in page: 379 of 2156x HRM.
ADSP-2156x SHARC+ Processor Hardware Reference (analog.com)