• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 100 subscribers
  • Views 342 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.

Boot DSP and Linux in parallel

Kalaiyarasan ES
Intellectual 680 points
Other Parts Discussed in Thread: OMAPL138, OMAP-L138

Hi,

  We are using omapl138 for our project, We want to boot DSP and Linux in parallel. How to do it?

If I have to boot DSP in UBL. what will be the changes need to do in UBL?

Please reply as earlier as possible

Thanks & Regards,

Kalaiyarasan

  • 0
    TI__Guru** 116770 points

    Kalaiyarasan,

    Yes, you can boot DSP and linux in parallel. There are couple of resources that you will want to take a look at.

    1. LED blink example on OMAPL138: This example brings DSP out of reset and sets entry point of the DSP application from which DSP can execute code.

    http://processors.wiki.ti.com/index.php/Boot_Images_for_OMAP-L138

    In  addition to that you also need to copy uboot from your boot media in your ARM UBL and after bringing DSP out of reset pass control uboot.

    2. Putting uboot in binary format is described in the linux PSP package. The PSP package will also contain an ARM UBL code. This version of the UBL only does the device, SDRAM, UART initialization and copies the uboot from the boot medium.

    http://software-dl.ti.com/dsps/dsps_public_sw/psp/LinuxPSP/DaVinci_03_21/index.html 

    The ARM UBL that you need should combine the UBL described in the two places.

    There are few things that you need to remember while creating your boot.

    • ARM UBL , DSP binary, uboot should not have any memory overlaps.
    • If you are not combining ARM UBL and DSP binary in the boot image (AIS image) creation, you will have to format DSP application file using out2rcpc or some other utility:

                    Refer: http://processors.wiki.ti.com/index.php/OMAPL138_StarterWare_Booting_And_Flashing#Booting_an_ARM.2BDSP_System

    • If you do combine the ARMUBL and DSP binary in the AIS file, your DSP code will be loaded in memory by the external memory but if the combined binary is greater than the offset where the ARM UBL expects to find the Uboot, you will have to make appropriate changes in the memory map of the boot media.

    For example: If you are booting from SPI flash,  TI software expects ubl to be at offset 0x00 and uboot at 0x10000 in the flash memory but if you combine ubl code with DSP application binary to create an AIS image that is 72KB, you will need to move the uboot loacation and modify the ARM UBL code where these offsets are hard coded.

    I hope the information helps you create your boot setup Let us know if you have any further questions that we can help you answer.

    Regards,

    Rahul

  • 0 in reply to Rahul Prabhu
    Intellectual 680 points

    Thanks Rahul,

                            I have downloaded PSP  package from link given above it has UBL spi.bin but doesn't have source .

    I have used older PSP package.  I need to know

    1. whether i need to do load DSP binary into DSP memory section(L2 RAM ,DDR, ...) in ARM ubl ?  ( by default  RBL load AIS format (UBL , DSP)binary in their respective memory)

    2. Can i able to use default U-boot image comes with PSP package? ( Whether i need to change anything uboot (Uboot environment address will be changed)? )

      Thanks & Regards ,

    Kalaiyarasan

  • 0 in reply to Kalaiyarasan ES
    TI__Intellectual 1280 points

    Hi Kalaiyarasan,

    As per Rahul's post, from the link
    http://processors.wiki.ti.com/index.php/Boot_Images_for_OMAP-L138

    Topic: Obtaining the software

    Here, "Sample code and bootable images: here"

    without quotes, you can download the ARM and DSP sample codes. In this code,
    in linker.cmd file, you can specify the data, code section in memory.

    The same way, you can specify the memory addresses.

    If your board is TI EVM, then you can use the default u-boot image. If the board is custom board,
    then need to change as per H/W changes.

    -Regards,
    Balaji N

  • 0 in reply to Balaji Nagarajan
    Intellectual 275 points

    Hi Balaji N，

     Where can  I get an example of i2c(omapl138) platform driver base on linux? In the linux kernel,there is a C file "i2c-omap.c",but it seems not match to omapl138 platform?

    Thank you!

    ZhongfengChen