• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 221 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.

-dDA8XXGEM in DSPLink configured for OMAP-L138?

Carl Miller
Intellectual 260 points
Other Parts Discussed in Thread: OMAP-L138, OMAPL138, DA8XX

Hi.  I've got DSPLink 1.65.00.02 configured for OMAP-L138 as follows:

 

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

 

When I'm compiling my DSPLink, I see the following defines thrown on everything compiled for the DSP side:

-dMAX_DSPS=1 -dMAX_PROCESSORS=2 -dID_GPP=1 -dOMAPL138 -dPROC_COMPONENT -dPOOL_COMPONENT -dNOTIFY_COMPONENT -dMPCS_COMPONENT -dRINGIO_COMPONENT -dMPLIST_COMPONENT -dMSGQ_COMPONENT -dMSGQ_ZCPY_LINK -dCHNL_COMPONENT -dCHNL_ZCPY_LINK -dZCPY_LINK -dPROCID=0 -dDA8XXGEM -dDA8XXGEM_INTERFACE=SHMEM_INTERFACE -dPHYINTERFACE=SHMEM_INTERFACE -dDSP_TSK_MODE

 

Why are -dDA8XXGEM and -dDA8XXGEM_INTERFACE in there?   They're causing all the sample apps to be compiled not to boot the DSP (DSP_BOOTMODE_NOBOOT), which I don't think is what I want.  As I understand it, that's for devices where the DSP boots first, and subsequently starts up the ARM.  The DA8XX family seems to operate this way, but it's the opposite on the OMAP-L138.  Am I correct in this assessment?

 

I'm having trouble getting the sample apps to run on the DSP, and I'm thinking it's because they're being compiled for the wrong boot mode due to that -dDA8XXGEM define.  Is that a plausible explanation?  Is there some reason why I would, in fact, want that define?  If not, how did it get there and how do I get rid of it?

 

Thanks much for any insights.

 

        --------Carl

  • 0
    TI__Genius 17355 points

    Carl,

    I'm not sure if this is going to answer your question or not, but I have two suggestions.  The first is to get the latest version of the DSPLink product, which I believe is 1.65.00.03.  The second is to get the latest OMAP-L138 DVSDK release and check how the DSPLink product is configured and built in that (it's not clear whether you are operating in the SDK environment or not - if so, then ignore the previous statement).  I don't think I've used the DSPLink samples before, but I have used DSPLink to create and build my own projects.  So I can't say whether there is an issue with how the examples build, but I can say that DSPLink itself works (I configure it with the same options).

    Regards, Daniel