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

DSP Link config for Codec Engine sanity_test

Dirk Helgemo
Intellectual 475 points
Other Parts Discussed in Thread: OMAP3530

FYI:  The pre-built sanity_test in Codec Engine 2.23.01 requires a specific configuration of the DSP Link driver, else it will not run (see here for details).  So if you must build your own dsplink driver, you'll need to match its configuration for it to be able to run. Specifically (at least for examples/apps/sanity_test/evm3530), I found that DSP Link's channels must be disabled.  In terms of the dsplinkcfg.pl configuration script (in dsplink/config/bin), this means setting the "--comps" argument to "--comps=ponslrm".  (Not sure whether you can reduce further, but it is definitely required to not have "c".  If "c" is present (thereby enabling DSP Link channels), running sanity_test/app.out results in the error shown here; DATA (channels) was not initalized by the DSP image.)  -Dirk

  • TI__Genius 17205 points

    Yep.  Note that the Link configs documented here...

        http://tiexpressdsp.com/index.php?title=Codec_Engine_Link_Config

    ... describe the Link config used both during validation _and_ when building the pre-built sanity_test examples.  As Dirk correctly mentions, we don't include 'c' (CHNL) in the Link configuration during our validation.

    FYI, for CE 2.24, in addition to removing 'c' (CHNL), we're strongly considering removing 'r' (RingIO) and 'n' (Notify) as Codec Engine doesn't utilize those Link features.  Note, this is just for CE validation - those features are still supported by the Link product, and can be enabled if used independent of CE.

    Chris

  • in reply to Chris Ring
    Intellectual 475 points

    Thanks for the cross reference, and the heads-up for the next Codec Engine.  -Dirk

  • in reply to Dirk Helgemo
    Prodigy 10 points

    Hi,

        I don't know what exactly `validation´ means. At the Codec Engine Link Config page, under OMAP3 and GNU Toolchain titles, the --comps parameter is given as below:

    perl $(DSPLINK)/config/bin/dsplinkcfg.pl --platform=OMAP3530 --nodsp=1 --dspcfg_0=OMAP3530SHMEM \
        --dspos_0=DSPBIOS5XX --gppos=OMAPLSP --comps=ponslrm --legacy=1

    Why is c missing?

    I'm working on OMAP3530. Using Openembedded, I've built dsplink 1.63. At the configuration phase, I set --comps=ponslrmc as dspconfig.pl parameter. When try to run loop or scale at OMAP3530, I get CHNL create () failed error. Note that all other samples (ringio, mplist, message etc) run flawless. In a mail-list archive, somebody proposed that the build procedure is executed as the Channel component disabled. Indeed, I check CURRENTCFG.MK and the last line is:

    export TI_DSPLINK_DSP_COMMON_DEFINES := MAX_DSPS=1 MAX_PROCESSORS=2 [...] CHNL_COMPONENT CHNL_ZCPY_LINK [...]

    Apparently, channel component is enabled. Do you have any idea?

    Regards