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.

TDA4VM: TDA4 GPU No display

Part Number: TDA4VM

hi expert

i use sdk 7.3 qnx+rtos

When I use SD card file system and test GPU display with gles3-gears the screen display is  ok.

but if i use emmc filesystem There is no display on the screen ,If mcu2-0 is not loaded during startup, the screen display is ok.

the definition of DSS already closed which in vision_apps ../ common/ mcu2-0 cfg 

From the log file there is no error in either the MCU log or the GPU screen log under QNX

What are the possible causes of the above problems

Best Regards

  • Hi,

    If the DSS is to be controlled by the A72, the steps mentioned in 4. PSDK QNX Components — Processor SDK QNX J721E (ti.com) should be followed.   These steps are used to control ownership of the DSS, A72 vs. R5.

    Regarding eMMC vs SD filesystem, one theory would be that the mount point being used for SD vs eMMC is different.  As such the environment variables, and/or command line parameters need to be adjusted accordingly to provide the correct paths. 

    At the end of the day as it pertains to GPU working/not working, the filesystem on the SD vs eMMC will not matter.

    Regards,

    kb

  • Hi,kb

    then i use emmc filesystem i found  something unusual like next log,if i use sd filesystem it‘s ok 

    and i searched DP fimrware maybe it  pointing to libWFDjacinto7,but this file in the path /usr/lib/graphics/jacinto7

    Jan 01 00:00:18.853 screen.114708 slog* 300 screen: starting up...
    Jan 01 00:00:18.854 screen.114708 slog 300 screen: Configuration file: /usr/lib/graphics/jacinto7/graphics.conf
    Jan 01 00:00:18.878 screen.114708 slog 200 [j7_wfd]INFO: external DP firmware not found, using driver defaults
    Jan 01 00:00:18.890 screen.114708..0 0 -----ONLINE-----

    My environment variables are as follows

    File properties are as follows

  • Hi,

    Please run a "pidin ar", and take a look at the path that screen is referencing for the graphics.conf:

    screen -c /ti_fs/usr/lib/graphics/jacinto7/graphics.conf.dss_on_r5

    If the -c option is not used then Screen would check for the GRAPHICS_ROOT env variable.

    When screen is launched, it will use environment variables present at the time it is launched, to determine library search path.  If launched from the BSP startup script, it would use the env variables from there (see build file).  If launched from local script, it may use env variables specified there.  If launched from command line it would use the local environment variables.

    Note that environment variables that are set within the shell script, do not persist back to command line.

    For testing, recommend you "slay screen", set your local environment variables , and then launch screen, to ensure you know what env variables are being used.  The /ti_fs/scripts/user__dss_on_a72.sh can be referenced for setting of variables.  Instead of running the script, copy and paste on command line.

    echo "user.sh called..."
    
    echo Setting additional environment variables...
    export PS1='J7EVM@QNX:$(pwd)# '
    export PATH=:/proc/boot:/bin:/sbin:/usr/bin:/usr/sbin:/opt/bin:/ti_fs:/ti_fs/bin:/ti_fs/sbin:/ti_fs/usr/bin:/ti_fs/usr/sbin:/ti_fs/tibin:/ti_fs/vision_apps:/ti_fs/scripts
    export LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll:/opt/lib:/ti_fs/lib:/ti_fs/usr/lib:/ti_fs/lib/dll/mmedia:/ti_fs/lib/dll:/ti_fs/tilib:/ti_fs/vision_apps:/ti_fs/usr/lib/graphics/jacinto7
    export GRAPHICS_ROOT=/ti_fs/usr/lib/graphics/jacinto7
    
    echo "Starting tisci-mgr.."
    tisci-mgr
    waitfor /dev/tisci 2
    
    echo "Starting shmemallocator.."
    shmemallocator
    
    echo "Starting tiipc-mgr.."
    tiipc-mgr
    
    echo "Starting tiudma-mgr.."
    tiudma-mgr
    
    echo "Start screen.."
    screen -c /ti_fs/usr/lib/graphics/jacinto7/graphics.conf.dss_on_a72
    echo "screen started with dss_on_a72 configuration.."
    

    Regards,

    kb