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

OMAPL137 - ARM/DSP Boot Loading

BenjaminRTC
Intellectual 365 points

I'm trying to get the sample applications for DSPLInk Version 1.61 to run in DSP_BOOTMODE_NOBOOT on the OMAPL137 EVM.  I believe I have properly built the sample applications for DSP_BOOTMODE_NOBOOT (as detailed in the DSPLink ProgrammersGuide.pdf and Install_Guide_Linux_OMAPL137xx.pdf) but I have some confusion on how flashing the DSP sample application will work/interact with the bootloaders.  From my understanding of how the ARM and DSP bootloaders work, the dsp bootloader is used to start the ARM bootloader which in turn starts u-boot for booting Linux. If I flash the dsplink (dsp-side) sample application will it overwrite the dsp bootloader and stop the ARM/Linux side from booting?   Is there any documentation that describes how to design/flash an application to boot on the dsp side and then start the bootloader on the ARM side of the part to boot up Linux?

Thanks

  • 0
    TI__Mastermind 27585 points

    It depends on where you flash the image. The serial flashing tool will always flash the image at address 0 of the flash. This will definitely overwrite the DSP bootloader, and depending on the size of the image, it could overwrite the ARM bootloader and u-boot as well.

    The source for the DSP and ARM bootloaders is included in the PSP package and can be rebuilt to search for the images in different locations. You could also modify the CCS-based flashing tools, also in the PSP package, to flash each image wherever you want.

    There is currently no documentation that covers this process however.

    Jeff

  • 0 in reply to jc-ti
    Intellectual 365 points

    Jeff,

    Thanks for your response.  As far as I can tell the DSPLink documentation didn't detail this caveat and thus it seemed like the flashing could be achieved with minimal effort. Since this flashing capability isn't already provided, is it safe to say that most everybody uses the Normal Boot Mode (ARM loads the DSP Side executable) of DSPLink to run DSP side code with an OMAP part?

    Regards,

    Tim

  • 0 in reply to BenjaminRTC
    TI__Mastermind 27585 points

    Typically DSP link applications are run from Linux. So you would still flash DSP_UBL->ARM_UBL->UBOOT on the SPI flash, and then store your Linux file system and kernel on a larger medium like SD/MMC card, or use TFTP for development. The DSPLink image would be stored inside the Linux file system rather than on the SPI flash.

    Jeff

  • 0 in reply to jc-ti
    Intellectual 365 points

    Jeff,

    Thanks for your help and insight.

    Tim

  • 0 in reply to BenjaminRTC
    TI__Expert 4930 points

    Tim

    The exact procedure to make DSP ready in No Boot mode is not documented as it vary for different customers. Customers may choose different ways to boot load DSP external to DSPLink.

    Deepali