• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 452 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.

Rebuilding/running the qtInterface app on the DM365 with DVSDK 4.01...

Chuck@Cimarron Systems
Intellectual 850 points

To all Qt experts,

In order to understand how Qt works with the DVSDK 4.x for the DM365, my goal is to make simple modifications to the qtInterface app.  As a starting starting point, I've tried to rebuild the qtInterface app by following the instructions for building Qt apps found at the bottom of page 16/top of page 17 of the SDG supplied with DVSDK 4.01 then run it in conjunction with one of the demo apps.  Starting with a clean qtInterface directory, here are the command line elements I have executed:

1. [linux-devkit]:~/ti-dvsdk_dm365-evm_4_01_00_09/dvsdk-demos_4_00_00_21/qtInterface> qmake -project

2. [linux-devkit]:~/ti-dvsdk_dm365-evm_4_01_00_09/dvsdk-demos_4_00_00_21/qtInterface> qmake

3. [linux-devkit]:~/ti-dvsdk_dm365-evm_4_01_00_09/dvsdk-demos_4_00_00_21/qtInterface> make PLATFORM=dm365

4. [linux-devkit]:~/ti-dvsdk_dm365-evm_4_01_00_09/dvsdk-demos_4_00_00_21/qtInterface> sudo cp qtInterface ${HOME}/targetfs/usr/share/ti/dvsdk-demos

5. root@dm365-evm:/usr/share/ti/dvsdk-demos# /etc/init.d/loadmodule-rc restart

6. root@dm365-evm:/usr/share/ti/dvsdk-demos# ./encode -v Avatar.264 -a Avatar.aac -o | tee log.txt

The qtInterface app returns the following: Failed to open /sys/devices/platform/omapdss/overlay0/enabled for writing

This makes no sense at all!  Why the reference to "omapdss" when my platform is the DM365?  What am I missing?  

So far my app development has gone relatively smoothly but this one has me puzzled - any help will be greatly appreciated.

BTW: my development platform is the EVMDM365.

Thanks,

-Chuck

 

  • 0
    Prodigy 130 points

    Your error output shows that you have mis-compiled the qtInterface with omap , not with dm365. Do not run "qmake -project" and "qmake" concurrently. "qmake -project" will rewrite your qtInterface.pro file.

    In original dvevm qtInterface.pro file , it defined platform

    HEADERS += messageserver.h \
     configwindow.h \
     controlwindow.h \
     osdmanager.h \
     qtinterface.h
    SOURCES += messageserver.cpp \
     controlwindow.cpp \
     configwindow.cpp \
     main.cpp \
     osdmanager.cpp
    RESOURCES += qtinterface.qrc

    #install
    target.path = /$(EXEC_DIR)
    INSTALLS += target

    QMAKE_CXXFLAGS_RELEASE += -DPlatform_$(PLATFORM)
    QMAKE_CXXFLAGS_DEBUG += -DPlatform_$(PLATFORM)

    CONFIG += thread link_pkgconfig

    With this  qtInterface.pro  file, you could compile the right version of qtInterface .

    Good Luck.

     

  • 0 in reply to jianmin zhang
    Intellectual 850 points

    Jianmin,

    Yes, I eventually figured this out...

    Thanks,

    -Chuck