• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 100 subscribers
  • Views 472 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.

DVSDK 3.10 w/ GStreamer on DM365

jason talley
Prodigy 200 points

I'm having a heck of a time getting what seems to be a trivial solution running.  So...

I've built the included kernel and am able to run the davinci video/audio demos.  I've also tried to build the latest kernel from the GIT tree, but Ir seems to be having issues.  The demos will not spawn b/c Ir (/dev/irqk) returns an error.

My ultimate goal is to get gstreamer running w/ DVSDK 3.10 on DM365.  If you have successfully tackeld this task, I'd appreciate you sharing your the versions of all the software you used and any changes you had to make. 

Most of the gstreamer things I have found seem to be based on the 2.10 SDK, but then there are other aspects that claim the TI plugin should work if DMAI builds -- which it does.

Thanks for any kicks in the right direction.

 

 

  • 0
    TI__Intellectual 910 points

    Jason,

    If you update to the latest kernel, you may need to re-build the irqk.ko module or it will not load.  In your DVSDK installation directory, update your Rules.make so LINUXKERNEL_INSTALL_DIR points to your updated kernel source, and type:

    make irqk_clean

    make irqk

    to re-build this module.

    Regarding GStreamer on DM365 using DVSDK 3.10 -- as you noted our current trunk still supports DVSDK 2.10.  If you're ok working with bleeding-edge development, there is a work-in-progress patch set available at http://gstreamer.ti.com/ that adds preliminary support for DVSDK 3.10.  On the project's front page, look at the first news item that talks about DVSDK 3.10 support.  If you click on it, it will give you a link to the page where patches are.  This patch set is in pretty good shape, but is still under development and is considered "use-at-your-own-risk".

    Thanks and regards,
    Don

     

  • 0 in reply to Don Darling
    Prodigy 200 points

    Hi Don,

       I am rebuilding the IRQK module and loading it and I still get the error.  The module loads fine.  I finally just commented out the IR_create call in the decode app.  It still fussed at me.  I haven't tried to debug why it fails.  Perhaps if I knew how to enable the dmai_err0 logs in the ir_create function I could narrow down the cause.  I don't quite fully understand everything that is being built as part of the DMAI - it may be possible that my ordering is causing grief, but it was a quicker solution to simply comment out the ir_create.  Finding the root cause is on my to-do list.

    Between the patches on the 3.10 tracker, the latest kernel, and a few tweaks and hacks, I've got the decode running - albeit with a few OSD glitches, and gstreamer running with basic audio/alsa test tone (I haven't tried the TI codec yet).  If there is anyone else working down this path, then I can post up some 1-liners of things I've done.  At this point tho, I'm not 100% sure I know every trick I've used. :)

    Would you even care to venture a guess at when 3.10 will be released?  Or let me ask it another way -- If I'm targetting a project deadline of Sept '10, would you recommend using the existing 2.x SDK?  Or will 3.10 be ready soon enough to.  At this point, I'm really in learning mode as I am fairly new to gstreamer and streaming in general.

     

    I understand these are use-at-own-risk - that's usually when the fun begins :).  Thanks for the response.

     

     

     

     

  • 0 in reply to jason talley
    Genius 5240 points

    So what?  Nobody knows how to enable dmai_err logging?  I would like to know too.

  • 0 in reply to John Anderson
    Genius 5240 points

    Found this....

    The DMAI modules have trace built in which can be enabled on Linux using the
    @c DMAI_DEBUG environment variable. Setting it to '1' prints errors and
    warnings, while setting it to '2' prints errors, warnings and debug
    messages. If you have a target application @e myapp which uses DMAI you
    can set this environment variable for just one invocation of the command
    by executing the following on the @b target in the bash shell:

    @verbatim
    > DMAI_DEBUG=2 ./myapp
    @endverbatim

    This will send the DMAI trace output to stdout.

    <ul>
    <li>DMAI_DEBUG=0 disables DMAI trace, even if it is set by Dmai_setLogLevel in the application itself.
    <li>DMAI_DEBUG=1: errors and warnings
    <li>DMAI_DEBUG=2: all messages
    </ul>

    @note CE_DEBUG can be used to independently set the debug level for the Codec Engine. It does not affect the debug level for DMAI.