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

Refernce to SDRAM in DSP/LINK library

John Wilkes
Expert 1315 points
Other Parts Discussed in Thread: OMAP-L138, OMAP-L137, OMAPL138

Hi,

Why is the symbol 'SDRAM' referenced in the DSP/LINK IPS module?

I am using an OMAP-L138 device and so my project uses the L138 XDC platform file. The sample projects provided with DSP/LINK use the OMAP-L137 platform. The only difference between these two platforms in XDC appears to be the name given to the external memory: L137 calls it SDRAM and L138 calls it DDR. When I link my project with the DSP/LINK libraries I get a linker error:

undefined first referenced                           

  symbol       in file                                

 --------- ----------------                           

 _SDRAM    ../../DspLink/Lib/DEBUG/dsplink.lib<ips.obj>

 

error: unresolved symbols remain

error: errors encountered during linking; "PicoBossDL.out" not built

If I use the L137 platform file in my project instead of the L138 file then the project compiles OK. This suggests that there is a reference to the SDRAM symbol in the IPS module (though I cannot see it in the source code for this module).

Have I got this right or have I missed something here? My code now compiles with the L137 platform so should I just ignore this? Or should I create my own platform?

Any help or comments appreciated.

Cheers,

John.

 

 

  • 0
    TI__Mastermind 22760 points

    John,

    The L137 has memory named SDRAM, whereas the L138 has it named DDR.  You should be able to configure and build DspLink samples for L138.  Are you using DspLink 1.65.00.03? Then you can just configure for L138 as follows:

    perl dsplinkcfg.pl --platform=OMAPL138 --nodsp=1 --dspcfg_0=OMAPL138GEMSHMEM --dspos_0=DSPBIOS5XX --gppos=ARM --comps=ponslrmc

    or
    perl dsplinkcfg.pl --platform=OMAPL138 --nodsp=1 --dspcfg_0=OMAPL138GEMSHMEM --dspos_0=DSPBIOS5XX --gppos=OMAPL138LSPuc --comps=ponslrmc

    Best regards,

        Janet

  • 0 in reply to janet
    Expert 1315 points

    Hi Janet,

    Excellent. That seems to have fixed the problem nicely, thank you for your response. I am using 1.65.0.0.3 but the user guide bundled with this is for 1.65.0.0.2 (LNK 058 USR) and it does not mention the OMAPL138 platform. Consequently, I built the libraries with platform set to OMAPL1XX and dspcfg_0 set to OMAPL1XXGEMSHMEM, hence my problem. Following your suggestion I can now build my application in CCS using the L138 platform and link in to the re-built libraries with no errors.

    Well, it compiles but does not work yet, but that is for another day and another forum post...

    Thanks again.

    Cheers,

    John.

  • 0 in reply to John Wilkes
    TI__Mastermind 22760 points

    John,

    That's strange.  I have an InstallGuide_Linux_OMAPL138.pdf in my 1.65.00.03 dsplink.  But I'm glad to hear that your app is building!

    Best regards,

        Janet