• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 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.

Codec engine 2.25 "STABS debug options" build issue

Monish Sonpal
Prodigy 170 points
Other Parts Discussed in Thread: TMS320DM6446

Hello,

I am trying to build codec engine 2.25.5.16 examples for the IC TMS320DM6446. I am using the following support components as given in the release notes:

BIOSUTILS - 1.2.2

EDMA3 - 1.11.0.2

FRAMEWORK COMPONENTS - 2.25.2.6

LINUXUTILS - 2.25.4.10

LPM_LINUX - 1.24.2.9

XDAIS - 6.25.2.11

BIOS - 5.33.03

and for building , I use the following tools

Codesourcery - 2009q1-203

Code Generation tools - 6.0.21.1

XDC tools - 3.10.03

I am doing this whole exercise of building CE examples to check whether the DSPLink 2.25's PROC module works and loads the DSP with DSP executable successfully as I was getting error code 0x80008052 while loading the DSP with one of the other encodecombo.x64P executable while using the DMAI's video encode example.

I had retained the version of Linuxutils 2.25 (CMEM), DSPLINK to 1.65.0.3 for building the codec engine examples while changing others.

Coming to the issue, while building the examples with "gmake" command from the viddec2_copy folder I get an error saying:

>> ERROR: Cannot use STABS debug options with 6400+

I went through the forums and found that it is the "-gp" option that creates the problem during the cl64P execution (linking process I believe).I don't get where to make the required changes to update the profile and coverage options manually (as suggested in the forums).

Although when running the same gmake from the "viddec_copy" folder, I don't get any build problems. I somehow couldn't figure this difference as I use the same xdcpaths.mak file @ examples/xdcpaths.mak  and xdcrules,mak file @ examples/buildutils/xdcrules.mak for all the example builds. I think it is something to do with the internal package.bld files inside the individual folders. Also I couldn't get from where is the -gp option passed. Where should I add the profile and coverage options manually? Will this solve the issue?

All sort of help is invited. Suggestions and opinions are also invited regarding debugging the DSPLink for successful DSP executable loading via DSPLink's PROC module as that is the final aim.  Special request to TI employees working on the codec engine, dsplink and related areas.

Thanks.

Regards,

Monish

  • 0
    Prodigy 170 points

    One more thing I noticed is that amongst all the examples' "codecs" folders, only few of the codecs have DSP side compiled library files inside the "lib"  folder within. Other examples don't. The codecs with the lib files are:
    viddec_copy,  videnc_copy ,  imgdec_copy, imgenc_copy, auddec_copy, audenc_copy, sphenc_copy, sphdec_copy, scale, g711, vidtranscode_copy, vidanalytics_copy, viddec2split_copy, universal_copy

    The ones that don't have these lib files are:

    viddec1_copy, viddec2_copy, videnc1_copy, imgdec1_copy, imgenc1_copy, sphenc1_copy, sphdec1_copy, audenc1_copy, auddec1_ires, auddec1_copy

    There are build issues only with the ones having no libraries. Why are these codecs folders lack libraries from which DSP executables can be made? Correct me if I am on the wrong track.

    Thanks.

    Regards

    Monish