• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 422 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.

How run independently LINUX and DSP for EVMC6747 (OMAPL137/TMS320C6747 Floating point)

Alexandre Amiez
Intellectual 270 points
Other Parts Discussed in Thread: OMAP-L137

Hello

I would like to run independently a LINUX on ARM and an in-house RealTime OS on DSP.

Using your boot procedure, DSP Boot (and application image) "DSP_AIS_Image"  is just a small loader in order to boot the ARM by loading ARM_UBL to L2 and by executing it. Then u-boot is loading and it is the real Linux boot. That it is clear and it is working fine. I got a running Linux.

Now by following the procedure "Flashing the C6747EVM" (http://wiki.davincidsp.com/index.php/Flashing_the_C6747_EVM), I am able to run the DSP with my application and my own RealTime OS from the SPI Flash.

I am wondering how can i mix both : a running LINUX on ARM and my own running OS on DSP ?

I would like to use LINUX and the DSP system  independently each other. But I do know how create a application image boot "DSP_AIS_Image" able to mix both.

If anyone is able to help me, it will be very helpfull.

Thanks for your help

Best regards

 

 

 

 

 

  • 0
    TI__Mastermind 24340 points

    Alexandre,

    Please see: http://community.ti.com/forums/p/7902/31972.aspx

    In summary, you can use/boot the DSP only, or you can use/boot the ARM only for OMAP-L13x.

    If you are going to use both, you will boot the ARM first and have Linux load an application on the DSP. In this case, you do not use ais for applications in the DSP side. What you do is to load a .out file (DSP executable) from Linux. For that you can use DSPLink or Codec Engine/IUniversal.

    For OMAP-L137 the DSP wakes up the ARM. Then, DSPAIS calls UBL (wakes up the ARM and puts the DSP in a RESEt state) that calls UBOOT that boots Linux. And Linux can load a DSP application.

    Please see the wiki page Omapl137/DA830 linux bootup for answers for OMAP-L137.

    Please also see chapter 12 of OMAP-L137 Applications Processor System Reference Guide

    If you are going to run just algorithms in the DSP, you might want to start with iUniversal (DSPLink will work too). If you are using the DSP drivers, you might want to start with DSPLink. If you use the drivers, you have to make sure that the ARM/Linux side does not interfere/use the same peripherals than the DSP. For example, you you are using McASP in the DSP, you have to disable the audio driver in the Linux Kernel and not use it. Also, make sure that you DSP application initializations are compatible with the Linux one (check pinmux conflicts etc).

     

  • 0 in reply to Mariana
    Intellectual 255 points

    Hello Mariana,

    you said:
    "For OMAP-L137 the DSP wakes up the ARM. Then, DSPAIS calls UBL (wakes up the ARM and puts the DSP in a RESEt state) that calls UBOOT that boots Linux. And Linux can load a DSP application."

    I need that my DSP application start quickly on reset. So I create my DSP application in AIS format and my DSP application calls UBL. The problem is that UBL put in reset the DSP blocking my DPS application. I modified UBL sources and I resolved this problem, but the same thing happen for Uboot and Linux. They put in reset the DSP. Is right? Must I modify also Uboot and Linux sources for prevent the reset  of DSP?

    Danilo