This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

I2C Slave Boot Mode Capabilities

Spruec6g, pg 14. describes  the I2C EEPROM boot mode which allows a sequence of Boot Parameter and Boot Configuration tables  to be provided to the bootloader.

We would like to use a similar sequence of Boot Parameter and Boot Configuration Tables but using the I2C slave boot mode.  Is this possible?

In particular we would like an FPGA to act as a I2C master and supply the Boot Parameter and Configuration tables to the C6455 acting as an I2C slave.  This is useful as an EEPROM is already on the C6455's I2C bus and this device cannot be used to hold boot data.

  • Paul,

    Section 2.3.5 I2C Slave Boot Mode says "The procedure is the same as Section 2.3.4, except for how the DSP receives data." Do you have questions about this section? It is brief.

    Regards,
    RandyP

  • Randy,

    Thanks for looking at this.  Specifically Spruec6g has,

    "In the I2C slave boot mode, the DSP is programmed as an I2C slave and waits for an I2C Master to send
    data, using a standard boot table format.
    The procedure is the same as Section 2.3.4, except for how the DSP receives data."

    My interpretation is that slave mode can be used to send boot tables (which contain the executable program) but not necessarily boot parameter tables or boot configuration tables.  Hopefully my interpretation is incorrect.  We wanted to be sure before committing to this boot architecture.

    thanks,

    Paul

  • Is it possible to transition from I2C boot mode to I2C boot mode using a boot parameter table?  For example, if the initial boot parameter table gives the value 0x7 (PCI boot) for the boot mode field, will the boot loader transition from I2c boot mode to PCI boot mode?  If not, what is the boot mode field used for in the I2C boot parameter table?

    thanks,

    Paul