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.

fc/edma3, fc/hdintc ERROR: Cannot use STABS debug options with 6400+/6740

Other Parts Discussed in Thread: OMAP3530

FYI:  Here is a potential fix for the following problem:

Context:  Codec Engine 2.23.01 for Linux, CodeGen 6.0.22 or 6.1.8, XDCtools 3.10.03.  Build target is OMAP3530.

When building these two drivers (in cetools/packages/ti/sdo/fc), the default scripts would fail when compiling for the DSP:

cl64P package/package_ti.sdo.fc.edma3.c ...
ERROR: Cannot use STABS debug options with 6400+
(CodeGen 6.1.8 also complains that 6740 would fail.)

The root cause of the issue is that the "-gp" option is being passed to the cl6x compiler for the xdc profiles of "profile" and "coverage", but this option is not supported for the DSP processor in OMAP3530.

I was able to fix this by changing the option to "--gen_profile_info" (for "profile") and "--codecov  --use_profile_info" (for "coverage") by inserting the following into examples/user.bld in the last "for" loop (labeled "specify custom toolchain options"; add an "if" similar to (and just after) the LONGNAME setting for GCArmv5T):

    if (t.name == "C64P") {
        // CodeGen (both 6.0.22 and 6.1.8) does not accept "-gp" for this processor,
        // as set by default by xdctools_3_10_03/packages/ti/targets/ITarget.xdc.
        // Change to options that are supported by cl6x of CodeGen 6.1.8.
        t.profiles["profile" ].compileOpts.copts = "--gen_profile_info";
        t.profiles["coverage"].compileOpts.copts = "--codecov --use_profile_info";
    }

So this combination seems to work for me.  With any luck, this will be helpful to someone else.

I'd love to hear of other combinations (especially newer ones) that might be easier.  -Dirk

  • Hi, I'm having the same problem, the is the script:

    ERROR: Cannot use STABS debug options with 6400+

    home/omap/work_amine/overo-oe//tmp/staging/i686-linux/ti-cgt6x-native/bin/cl6x -c  -qq -pdsw225 -mv64p -eo.o64P -ea.s64P  -Dxdc_target_name__=C64P -Dxdc_target_types__=ti/targets/std.h -Dxdc_bld__profile_coverage -Dxdc_bld__vers_1_0_6_0_21 -gp  -I. -I../../../.. -I/home/omap/work_amine/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/ti-codec-combo-omap3530-3161-r12/omap3530_dvsdk_combos_tspa_3_16_01 -I/packages -I/home/omap/work_amine/overo-oe//tmp/staging/overo-angstrom-linux-gnueabi/ti-codec-engine/cetools/packages -I/packages -I/home/omap/work_amine/overo-oe//tmp/staging/overo-angstrom-linux-gnueabi/ti-codec-engine/cetools/fctools/packages -I/home/omap/work_amine/overo-oe//tmp/staging/i686-linux/ti-dspbios-native/packages -I/packages -I/home/omap/work_amine/overo-oe//tmp/staging/overo-angstrom-linux-gnueabi/ti-codec-engine/cetools/packages -I/home/omap/work_amine/overo-oe//tmp/staging/overo-angstrom-linux-gnueabi/ti-codec-engine/cetools/packages -I/home/omap/work_amine/overo-oe//tmp/staging/overo-angstrom-linux-gnueabi/ti-codec-engine/packages -I/packages -I/home/omap/work_amine/overo-oe//tmp/staging/overo-angstrom-linux-gnueabi/ti-codec-engine/cetools/packages -I/home/omap/work_amine/overo-oe/tmp/staging/i686-linux/ti-xdctools-native/packages -I../../../.. -I/home/omap/work_amine/overo-oe//tmp/staging/i686-linux/ti-dspbios-native/packages/ti/bios/include -I/home/omap/work_amine/overo-oe//tmp/staging/i686-linux/ti-cgt6x-native/include -fs=./package/lib/lib/coverage/edma3/package -fr=./package/lib/lib/coverage/edma3/package -fc package/package_ti.sdo.fc.edma3.c

     

    ERROR: Cannot use STABS debug options with 6400+
    | make[1]: *** [package/lib/lib/coverage/edma3/package/package_ti.sdo.fc.edma3.o64P] Error 1
    | gmake: *** [packages/ti/sdo/fc/edma3,.libraries] Error 2
    | make: *** [.all-packages] Error 2

     

    My question is which file you have edited?

    thanks in advance

    PS: I 'm working to implment gstreamer Ti plugins on OMAP3530

     

     

  • Heh, looks like I never did mention the file name!  [:)]  (I'll go back and insert this into my original post, too.)

    For Codec Engine 2.23.01, the insertion was near the end of examples/user.bld.

    See also "What is build profile "debug_trace"? (used by fc/rman/examples)" at http://e2e.ti.com/forums/p/6700/26032.aspx about noticing how the xDAIS Framework Components (FC) build is rather different from the CE build (FC has its own config.bld if you get it as an independent package).

    Looking ahead:  As of Codec Engine 2.24, there is no "user.bld" file anymore, but I don't need seem to need this modification either.  Fortunately, the pre-built libraries work for me now, so I don't need to rebuild them.  That said, I also get the impression that the build system for FC has been stripped.

    Good luck!  -Dirk

    P.S.:  DMAI got in my way of implementing GStreamer on the GIT kernel (based on TI's OMAP35x Linux PSP 2.x).  The latest DMAI wants the old kernel interfaces (TI's OMAP35x Linux PSP 1.x).  The best document I've seen to describe the kernel changes (redesigned sysfs and transitioned to V4L2 ioctls) is the MigrationGuide pdf inside TI's OMAP35x Linux PSP 2.x package.