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.

Omap Example in DVSDK

Hi all

  I am currently working on Arm - Dsp communication,i downloded Dvsdk .

1.  when i run the h.264 sample decoder pjt present in omap example in dvsdk ,in simulator it is hanging near decode one frame(PROCESS() ;function). what would be the problem?

2.In the same pjt BCACHE funtions are present ,How they will work without DSP/BIOS configuration?

3 To make the XDAIS complaint i studied srpu360e doc and executed sample FIR example ,in that  the following errorrs i noticed

     ->main() and other global variables  must be XXX_TI_xxx  in this type.

     -> Rule 20 stack problem.(How eliminate this , i executed DM examples in XDAIS , again  rule 20 and rule 12 ialg problems,i already posted the problems in previous scarp, but i didnt  make reslolve)

Please Help me regarding above problems,

Thanks and regards

sureshkumar

  • sureshkumar said:
    1.  when i run the h.264 sample decoder pjt present in omap example in dvsdk ,in simulator it is hanging near decode one frame(PROCESS() ;function). what would be the problem?

    Which particular example are you looking at, is this one of the codec validation tests from wthin the DVSDK Combos folder? In this case I suspect your problem is the use of the simulator, as this codec depends on hardware outside of the C64x+ core itself to execute, hardware which the simulator does not support, it will most likely fail if used in the simulator, you may want to try the project on hardware. Also note that these tests have no support for ARM-DSP communication, these are meant to test the codecs themselves in a stand alone DSP only setup.

    sureshkumar said:
    2.In the same pjt BCACHE funtions are present ,How they will work without DSP/BIOS configuration?

    They will not work without BIOS, most of the software collateral provided by TI depends upon DSP/BIOS running on the DSP. Theoretically you could use the DSP without BIOS however this would mean you have to provide a lot of your own software frameworks, such as cache functionality to replace BIOS and an interprocessor ARM-DSP communication mechanism to replace Codec Engine and Link, thus we highly recommend the use of BIOS.

    sureshkumar said:
    3 To make the XDAIS complaint i studied srpu360e doc and executed sample FIR example ,in that  the following errorrs i noticed

    These errors could come from a few causes, the first being if you re-built the FIR example and had the -g and/or -ml3 option in the build options than you may be missing debug information that the QualiTI tool uses to verify. Secondly you will need to ensure that there are no spaces in the path used for the code gen tools if you are running this test in Windows, this can cause QualiTI failures.

  • Thank you very much, today i cleared all fails in QualiTI and tring to write my own code.

    One more doubt what is  eXpressDSP Component Wizard and wher do we find this?

  • ExpressDSP Component Wizard has been trimmed out of the XDAIS package deliverable, there is a small FAQ on this on the TIExpressDSP Wiki. Essentially the tool is considered outdated, and has largely been replaced by the QualiTI tool.