• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 510 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.

SPI EEPROM for 5515

Doaa Khattab
Prodigy 20 points
Other Parts Discussed in Thread: TMS320VC5505

please , does the Boot Loader know the sequence to read the application program that i will write in the SPI EEPROM  as there are instructions needed to be given to it before reading so is the boot loader know this sequence ...

my SPI EEPROM is (M95512-DRM95512-R M95512-W) and this is the used EEPROM in the kit 

thanks in advance

  • 0
    TI__Genius 13045 points

    Doaa,

    There should be a bootloader app note released soon which will have all the information required to develop the binary file that needs to be flashed into the EEPROM.  Generically you develop you application using Code Composer Studio to create a .out file.  Then you convert the .out to a binary file using the hex55.exe utility which is part of the Code Generation Tools package that comes with Code Composer Studio.  The utility will prepare the binary file so it can be read by the bootloader.

    The C5000 Team will have to comment on when the App Note will be available.  Until it comes out you can use the App Note for the TMS320VC5505 bootloader which is similar.  You can find the app note here: http://www-s.ti.com/sc/techlit/sprab92.

    Regards.

  • 0 in reply to TommyG
    Prodigy 20 points

    thanks so much Tommy

  • 0 in reply to Doaa Khattab
    TI__Guru 55325 points

    Hi Doaa,

    The boorlader SPI EEPROM support remains the same in VC5505 and C5515.

    16-Bit SPI EEPROM

    The bootloader supports booting from an SPI EEPROM with the following requirements for the external device…

    ·            The device must support at least a 500kHz SPI clock.

    ·            The device must be connected to SPI CS0 and act as an SPI slave.

    ·            The device uses 2 bytes (16 bits) for internal addressing (up to 64kB).

    ·            The device must have the capability to auto-increment its internal address counter to allow sequential reads from the device.

    ·            The device may be connected to either valid pin-mapping for SPI (there are 2 distinct pin-mappings available).  The bootloader attempts to communicate on each SPI pin-mapping, one at a time.

    Best regards,

    Ming