• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 748 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.

I have a question about C5515 boot loader.

da
Expert 2780 points
Other Parts Discussed in Thread: TMS320C5515


< From Using the TMS320C5515 / 14/05/04 Boot Loader(sprabd7c.pdf) >

Although encrypted boot of 24bit SPI EEPROM has been removed, what reasons How is this?
 > Encrypted boot is supported image of up to 64k byte?
 > 24bit SPI EEPROM Encrypted & Requesting boot code in the boot loader did not exist?

There is a description of the work area to the Note on page 2, but the memory is not used other address?

NOTE: SARAM31 (byte address 0x4E000 - 0x4FFFF) is reserved for the bootloader.

  • 0
    TI__Genius 12575 points

    Hi,

    Not sure whether I completely understood your questions, but let me try answer based on what I could gather. 

    • Boot both encrypted and unencrypted images from NOR, NAND, 16-bit SPI EEPROM, Flash, and I2C EEPROM, except for 24 bit SPI serial flash which supports only unencrypted images.
    • With respect to 16-Bit Serial Peripheral Interface (SPI) EEPROM, The device uses 2 bytes (16 bits) for internal addressing (up to 64kB).

    With respect to - SARAM31 (byte address 0x4E000 – 0x4FFFF) is reserved for the bootloader, Yes this is reserved for the bootloader. After the boot process is complete, this memory space can be used.

    Let me know if you have further questions on this.

    Regards

     Vasanth

  • 0 in reply to Vasantha K
    Expert 2780 points

    Hi,

    We SPI EEPROM was found because 64k bytes.

    If when you boot from NAND or MMC / SD, or will the handle 64k bytes or more of encryption image?

  • 0 in reply to da
    Guru 19890 points
    Hello,

    What da wants to clarify is whether C5515 Bootloader can handle larger encrypted image than 64kbytes if users would select another massive boot device such like NAND, MMC, etc.
    I believe the size restriction is originated from address generation to SPI EEPROM in ROM Bootloader and there is no restriction/known issue in decryption algorithm itself. Correct, right ?

    Best Regards,
    Naoki Kawada
  • 0 in reply to Naoki Kawada
    TI__Genius 12575 points

    Hi Naoki Kawada-san,

    Below is my response.

    Q1.What da wants to clarify is whether C5515 Bootloader can handle larger encrypted image than 64kbytes if users would select another massive boot device such like NAND, MMC, etc. 

    VK: Yes, that's correct. The limit in this case applies with respect to Internal RAM size. Further,

    • Boot both encrypted and unencrypted images from NOR, NAND, 16-bit SPI EEPROM, Flash, and I2C EEPROM.
    • Boot encrypted images from MMC/SD and USB.

    Q2. I believe the size restriction is originated from address generation to SPI EEPROM in ROM Bootloader and there is no restriction/known issue in decryption algorithm itself. Correct, right ?

    VK:  Yes .

    Hope this clarifies.

    Regards

     Vasanth

  • 0 in reply to Vasantha K
    Guru 19890 points
    Hi Vasanth,

    Thanks for your quick reply. We'll talk with our customer.

    Best Regards,
    Naoki Kawada