Re: when and where in the code the RBL call the IBL

Hi,

In the EVM, the FPGA is programmed to boot IBL, execute the PLL fix, and then jump right back to RBL for the set boot mode.
Ex: The bootmode is fed to DSP from FPGA . The IBL Init reads this info from the FPGA via SPI interface .The initial boot is forced to I2C at 0x51 by FPGA to take care of PLL workaround.
The PLL settings(multiplers/dividers ) are defined in I2cConfig.gel . The DevicePllConfig function uses these settings to configure Main,DDR and PASS PLL .

IBL is designed as a two stage bootloader, the iblinit and the iblmain. The iblinit does the PLL initialization and executes a PLL workaround code to get around a silicon bug in revision 1.0 chips and jumps back to Boot ROM for non I2C boot modes. The ibl main is the main bootlaoder that does pulls ELF data from the boot device (NAND/NOR/TFTP ..) and launches it.

For more information refer the Keystone ROM Boot Reference code:
processors.wiki.ti.com/.../Keystone_Device_Architecture

Thanks,

Hi,

Yes, the RBL always runs on the device first. There is no way to bypass this sequence. The RBL will load the IBL from I2C into device internal memeory (L2, MSMC) and then pass control to IBL. After the IBL does the PLL fix, it can choose to re-enter ROM or execute code from iblmain.

Thanks,