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

TDA4VM: GL SRV: ERROR: Couldn't open egl window!

zheng huicheng
Prodigy 200 points
Part Number: TDA4VM

Hi TI Experts，

     When I use the SRV node, the following error occurs:

EGL: has_extension: EGL_EXT_client_extensions EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses EGL_KHR_debug EGL_EXT_platform_wayland EGL_MESA_platform_gbm       EGL_MESA_platform_surfaceless
libEGL warning: No hardware driver found, falling back to software rendering
EGL: version 2096562176.0 ret: 0
EGL: eglInitialize() returned 0
EGL: after eglInitialize() eglError (0x3001)
EGL: ERROR: eglInitialize() failed !!!
149.233403 s: VX_ZONE_ERROR:[tivxOpenglGlSrvEglInfo:150] GL SRV: ERROR: Couldn't open egl window!
Grapy verify done!
App Verify Graph Done!
App Gpu Run!

       The SDK version used here is ti-processor-sdk-linux-automotive-j7-evm-07_00_00, I find that the path ~/ti-processor-sdk-linux-automotive-j7-evm-07_00_00/board-support/extra-drivers does not have the module ti-img-rogue-driver.So I copied it from the SDK of 7.03 to 7.00，then /dev/dri can be found in EVM board.But When I use the SRV node, the following error occurs. At present, we can not switch the SDK to a higher version due to the project. Is there any other way to successfully mount GPU on version 7.00?

       Looking for your reply!

     

  • 0
    Prodigy 200 points

    Hi TI experts，

    The following is the printing information when the GPU driver is mounted，

    [ 8.541495] PVR_K: 306: Read BVNC 22.104.208.318 from HW device registers
    [ 8.554529] PVR_K: 306: RGX Device registered with BVNC 22.104.208.318
    [ 13.225585] PVR_K: 1063: RGX Firmware image 'rgx.fw.22.104.208.318' loaded
    [ 13.239240] PVR_K:(Error): 1063: RGXGetFWImageAllocSize: FW info version mismatch (expected: 1, found: 33554432) [105]
    [ 13.272680] PVR_K:(Error): 1063: RGXGetFWImageAllocSize: FW info header sizes mismatch (expected: 32, found: 117440512) [105]
    [ 13.289586] PVR_K:(Error): 1063: RGXGetFWImageAllocSize: FW layout entry sizes mismatch (expected: 24, found: 1040306176) [105]
    [ 13.307264] PVR_K:(Error): 1063: RGXGetFWImageAllocSize: Not enough storage for the FW layout table (max: 8 entries, found: 369098752) [105]
    [ 13.322472] PVR_K:(Error): 1063: RGXGetFWImageAllocSize: FW page size mismatch (expected: 65536, found: 0) [105]
    [ 13.350463] PVR_K:(Error): 1063: InitFirmware: RGXGetFWImageAllocSize failed [833]
    [ 13.366473] PVR_K:(Error): 1063: RGXInit: InitFirmware failed (3) [1366]
    [ 13.382447] PVR_K:(Error): 1063: RGXInit() failed (PVRSRV_ERROR_INVALID_PARAMS) in PVRSRVCommonDeviceInitialise() [2343]
    [ 13.400700] PVR_K:(Error): 1063: PVRSRVDeviceFinalise() failed (PVRSRV_ERROR_NOT_INITIALISED) in PVRSRVCommonDeviceInitialise() [2352]
    [ 13.418450] PVR_K:(Error): 1063: PVRSRVDeviceOpen: Failed to initialise device (PVRSRV_ERROR_NOT_INITIALISED) [461]
    j7-evm login: [ 16.270799] PVR_K:(Error): 1255: PVRSRVDeviceOpen: Driver already in bad state. Device open failed. [450]

  • +1 in reply to zheng huicheng
    TI__Expert 8385 points

    Hello,

    Yes, we see that ti-img-rogue-driver is missing in 07_00_00 version of the SDK. The version is 07_03_00 is not compatible with 07_00_00. You can try  the version provided with 07_00_01. We do however recommend just upgrading to a later SDK and that will have the kernel module.

    Alternatively, you can clone the driver repository:

    https://git.ti.com/cgit/graphics/ti-img-rogue-driver

    You can clone this to: <sdk>/board-support/extra-drivers/ti-img-rogue-driver-1.10.5371573

    You can checkout branch: linuxws/zeus/k5.4/1.10.5371573,

    Apologies for the inconvenience.

    theOnce again -  it is always best to just upgrade to a newer SDK.

    Regards

    Hemant