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

OMAP-L137 spi boot (D800K001)

Andrea Paterniani
Prodigy 60 points
Other Parts Discussed in Thread: OMAP-L137

Hi all,

My target board is booting via SPI slave.

I'm tuning boot speed so I need to konw timing requirements of D800K001 spi slave routine.

To be more precise I need the relationship between OMAP core clock, SPI clock frequency and delay beetween words to avoid SPI overrun.

Also the same data for D800K003 (if different).

Thanks

Regards,

Andrea

  • 0
    TI__Expert 8150 points

    Have you referred the device datasheet? What information you believe is missing?

    Cheers,
    Gagan 

  • 0 in reply to Gagan Maur
    Prodigy 60 points

    My references are sprab04f.pdf and obviously OMAP-L137 datasheet / user guides but I cannot find material on bootloader FW.

    In my test I observe that time between words is crucial.

    As sprab04f NOTE (pag. 22) remarks there are also problem sending commands too early.

    I'm searching for detailed info on what to expect at certain core frequency.

    For example @ 300 MHz core frequency, which delay between words must be granted to avoid overrun?

    How delay depends on CRC computation?

    Is there any available formula?

    Is it possible to view bootloader source code?

    To sum up I need to define safe and fast boot procedure regardless of specific AIS file.

    Regards,

    Andrea

  • 0 in reply to Andrea Paterniani
    TI__Expert 8890 points

    Andrea,

    You can find more information about SPI slave boot using the d800k001 ROM bootloader in this wiki article:

    Unfortunately, we don't have a formula for estimating the lowest required delay between SPI read/write operations.  As you surmise, it will depend on the CPU speed and whether or not CRC is enabled.  I will forward this request to the engineers responsible for supporting the bootloader.

    The required delay between AIS opcodes depends primarily on what the previous opcode was.  For example, the function execute opcode generally takes longer than the section load opcode.  The long, required delays between opcodes were considered to be a bug, and this was addressed in the d800k003 ROM revision.

    The bootloader source code is not available for download.

  • 0 in reply to Joe Coombs
    Prodigy 60 points

    I already had a look at the wiki page you suggest; unfortunately the infos I need are missing.

    You tell me that D800K003 solves delay bug, but sprab04f refers also to D800K003 and contains the note on delay bug.

    Can you confirm that the bug is solved in D800K003?

    Thanks,

    Andrea