• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 214 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.

Original question:

TDA4VM: Question about the version of the qnx screen board support packages

TDA4VM: Screen crash is observed when running graphics.conf in EVK board

Mahesh kakani
Prodigy 110 points
Part Number: TDA4VM

Hi Team,

This query is related to 

01: TDA4VM: Screen Command behavior/test result on J721E board - ZF Jacinto Forum - ZF - EP Automotive - TI E2E support forums. 

02: TDA4VM: Question about the version of the qnx screen board support packages - Processors forum - Processors - TI E2E support forums

As per point:02, i have tested packages i.e 

--> V3.2 of screen board.

--> V3.0 of Null driver from Ran Jing (original owner for above point:02)

Tested the screen command i.e screen -c /usr/lib/graphics/jacinto7/graphics.conf.  I have observed crash once again as mentioned in 01.

i have multiple questions on this:

01: We have graphics.conf.dss_on_r5 at psdkqa/qnx/scripts/usr/lib/graphics/jacinto7/graphics.conf.dss_on_r5, Is this the .conf, that was used by TI in testing the "screen -c" command?

02: Does it runs on R5?

03: Can you please share the command that was used to test the "screen -c" command?

04: As per - screen (qnx.com), the .conf file shall be graphics.conf, Where can i get the graphics.conf file? Is it similar to "raphics.conf.dss_on_r5"?

Regards,

Mahesh.

  • 0
    TI__Guru** 121311 points

    Hi Mahesh,

    1) When screen is launched and references the file "graphics.conf.dss_on_r5", that particular graphics configuration file is letting Screen know, that Screen is responsible for GPU, and screen will launch any applicable GPU driver / OpenGL libraries.   The "graphics.conf.dss_on_r5", would reference the dummy WFD driver meaning the A72 based Screen driver will not touch the DSS H/W module.   In this case, the DSS is expected to be controlled by the TI SDK S/W running on the R5, or not used at all.  See below link on SDK documentation:

    2)  See (1).  Note that the vision apps build environment also has build flags, which allow for modifying the control of the DSS see Vision Apps User Guide: Build Instructions search on DSS.

    3) The psdkqa/qnx/scripts/user_xxx.sh for the SDK QNX under test can be referenced to see how screen was launched in TI verification.

    4) QNX includes a graphics.conf file with its Screen package delivery.    The TI SDK QNX provides examples of graphics.conf files which can be used to enable TI Vision Apps demos.

    Regards,

    kb

  • 0 in reply to KB
    Prodigy 110 points

    Hi KB,

    Thanks for the information

    Can you please share me some inputs..

    01: Do we need to compile the VisionApps? Does it have any dependency with the Screen package?

  • 0 in reply to Mahesh kakani
    TI__Guru** 121311 points

    Hi Mahesh,

    The build environment for Vision Apps for QNX, will build PSDK QNX.   The screen installation will be required for the full build to work.

    If the desire is to run Vision Apps without Screen being installed, then modifications to build environment would be required.

    Is a build issue being seen?  If so please provide build logs.   

    Regards,

    kb