Other Parts Discussed in Thread: OMAPL138, OMAP-L138, OMAP-L137
I'm trying to rebuild the DSP Link for the OMAPL138.
I have Installed the software packages (http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/omap_l138/1_00/latest/index_FDS.html) as specified in http://tiexpressdsp.com/index.php/GSG:_Installing_the_Software_for_OMAP-L138.
I do the following before attempting to build the DSP Link
- SDK Software installed
- MV Tools installed
- Linux kernel configured and built
I build the SDK successfully... Then, I attempt build DSP Link by following this guide, http://tiexpressdsp.com/index.php/Building_The_OMAP-L137_SDK.
I don't know what to do in step 2 of the Building the DSP Link section.
Step 2: Configure what platform you are building DSPLink for; this is done by invoking a perl script included with DSPLink. For example, to build DSPLink using MV5 GNU tool chain, go to DSPLink root directory invoke the following command:
host $ cd /home/<useracct>/OMAPL137_arm_1_00_00_10/dsplink-1_61_03-prebuilt/packages/dsplink
host $ perl config/bin/dsplinkcfg.pl --platform=OMAPL1XX --nodsp=1 --dspcfg_0=OMAPL1XXGEMSHMEM --dspos_0=DSPBIOS5XX --gppos=MVL5G --comps=ponslrmc --DspTskMode=1
I want to use the Sourcery G++ tools from Code Sourcery instead of the Montavista Linux toolchain. However, this toolchain is not part of the gppos options of the dsplinkcfg.pl script. Would I have to add a new definition for the Sourcery G++ tool in the dsplink.pl? Can you advice on what things I would have to edit in this perl script?
