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
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).
ALL CONTENT AND MATERIALS ON THIS SITE ARE PROVIDED "AS IS". TI AND ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY OF THESE MATERIALS FOR ANY PURPOSE AND DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THESE MATERIALS, INCLUDING BUT NOT LIMITED TO, ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL PROPERTY RIGHT. NO LICENSE, EITHER EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, IS GRANTED BY TI. USE OF THE INFORMATION ON THIS SITE MAY REQUIRE A LICENSE FROM A THIRD PARTY, OR A LICENSE FROM TI.
Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI and its suppliers reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.