• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 101 subscribers
  • Views 462 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Can anyone tell me how to use omapl138 ARM&DSP communication in Qt project?

user4174595
Prodigy 10 points
Other Parts Discussed in Thread: OMAPL138, DM3730, OMAP3530

hi,

Now I have a omapl138 development board,with Linux 2.6.33,Qte 4.7 ,It works well. I already know omapl138 use DSPLINK or SYSLINK to let ARM and DSP cores communicate ,I already build the dsplink`s examples program and run in my board successful .

But I don`t know how to use DSPLINK in my Qt project,I've read the same question :

http://e2e.ti.com/support/embedded/tirtos/f/355/t/118396.aspx

It seems use the DVSDK will solve my question ,but  how?

Yes the wiki says to include DVSDK's libs and path in Qt project will be ok , and after that , what should i do ? How it will work?

Was it will just let use the dsplink's APIs?Or I was thinking wrong?

After all ,I was wonder is there anyone who have a Qt project example include those libs or anything else , using one way to shows me how to use DSPLINK in Qt project to make ARM&DSP communicate .(I want ARM can get DSP's data and DSP can get ARM's control command ,) 

Or anyone who can give me some advice to get such an example?

Thanks !

  • 0
    TI__Genius 12865 points

    Hi user4174595,

    The closest example I know of is one that is incidentally provided as part of the Linux DVSDK 4.03 for DM3730: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_4_00/latest/index_FDS.html

    Under the directory dvsdk-demos_4_02_00_01, there is a demo that is constructed with a QT 'front end' process that drives the UI, which can launch the selected DVSDK encode/decode application as a separate 'back end' process. The 'front end' executable is written in C++ with QT support, and is located in the 'qtInterface' subdirectory. It communicates with the decode demo in the omap3530/decode subdirectory using named pipes, and the latter uses the standard DVSDK software stack including DSPLINK to render the video by communicating with the codec on the DSP.

    You may want to study it to see if it helps.

    Best regards,

    Vincent