• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 2 answers
  • Subscribers 99 subscribers
  • Views 486 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

XEVMK2EX: use of EEPROM on K2E EVM

Tarang Jindal68
Intellectual 820 points

Part Number: XEVMK2EX

Hello, 

What is the use of EEPROM on K2E EVM. 

We want to support SPI NOR Flash for the booting purpose on our board. can we avoid I2C EEPROM or is it necessary to keep EEPROM?

If we do not provide EEPROM on our board, what will be the consequences ? 

is EEPROM related to second stage bootmode? 

Please clear. 

Thanks and Regards

Tarang Jindal

  • 0
    TI__Guru**** 161600 points
    Hi Tarang,

    What is the use of EEPROM on K2E EVM.


    This and the other questions are explained in the K2E EVM Technical Reference Manual (https://www.einfochips.com/wp content/uploads/2016/04/EVMK2E_Technical_Reference_Manual.pdf), see Section 2.6 I2C Boot EEPROM / SPI NOR Flash:

    "The I2C modules on the 66AK2EX will be used by the DSP to control local peripheral ICs (DACs, ADCs, etc.) or may be used to communicate with other controllers in a system or to implement a user interface.
    The I2C bus is connected to one EEPROM and to the 120-pin expansion header (CN7). There are two banks in the I2C EEPROM which respond separately at addresses 0x50 and 0x51. These banks can be loaded with demonstration programs. Currently, the bank at 0x50 contains the I2C boot code and PLL initialization procedure and the bank at 0x51 contains the second level boot-loader program. The second level boot-loader can be used to either run the POST program or launch the OOB demonstration from NOR flash memory.
    The serial peripherals interconnect (SPI) module provides an interface between the SoC and other SPIcompliant devices. The primary intent of this interface is to allow for connection to a SPI ROM for boot. The SPI module on SoC is supported only in Master mode.
    16MB NOR FLASH (part number N25Q032A11 from NUMONYX) is attached to CS0z on SoC. It contains demonstration programs such as POST or OOB demo. The CS1z of SPI is used by the DSP to access registers within BMC."

    Best Regards,
    Yordan
  • 0
    TI__Guru** 116170 points
    Tarang,

    The EEPROM on the EVM was populated as it is one of the media from which this device can boot from but unlike Keystone I or C66x devices the EEPROM on the EVM is not required during boot or for loading IBL/work arounds. On your custom board, you are free to eliminate I2C EEPROM if you don`t have any use for it.

    Please note the device boots with PLL in bypass from SPI NOR and I2C boot modes so these are relatively safe boot modes to boot from. To speed up the boot from either of these boot media, you will need to use SPI parameter table. Also, note unlike Keystone I devices K2E is an ARM master boot device so the ARM will boot first and the DSP needs to be woken up.

    IF you have questions of how to create boot images for this device refer to the following links for tools and documentation:
    processors.wiki.ti.com/.../KeystoneII_Boot_Examples
    processors.wiki.ti.com/.../L

    I hope this helps clarify all your questions.

    Regards,
    Rahul