AM625: AM6254 GPU Cannot find EGLConfig

Zhang Hang

Part Number: AM625

Tool/software:

Hi TI

We want to use the AM6254 GPU and found the GPU driver source code in TI's SDK directory: INSTALL_PATH/ti-processor-sdk-linux-am62xx-evm-09.02.01.10/board-support/extra-drivers/ti-img-rogue-driver-23.3.6512818. I compiled the driver source code and obtained pvrsrvkm.ko. The pvrsrvkm.ko module was also successfully loaded. The relevant print logs are as follows:

[    2.837653] pvrsrvkm: loading out-of-tree module taints kernel.
[    2.850545] PVR_K:  325: Device: fd00000.gpu
[    2.850744] PVR_K:  325: Read BVNC 33.15.11.3 from HW device registers
[    2.850839] PVR_K:  325: RGX Device registered with BVNC 33.15.11.3
[    2.852054] [drm] Initialized pvr 23.3.6512818 20170530 for fd00000.gpu on minor 1

The output of the lsmod command is as follows:

root@am62xx-evm:~# lsmod
    Tainted: G
pvrsrvkm 1163264 0 - Live 0xffff800000a40000 (O)
root@am62xx-evm:~#

The output of the rgx_triangle_test command is as follows:

root@am62xx-evm:~# rgx_triangle_test
Connecting to first (0) default pvr device
Selected display mode: 1024x600@59
----------------------- Start -----------------------
Using display type: DRM/KMS
Window created with 2 buffers
Frame number 0
Frame number 100
Frame number 200
Frame number 300
Frame number 400
Frame number 500
Frame number 600
Frame number 700
Frame number 800
Frame number 900

Total time: 16882ms
Mean time per frame: 16899us
FPS: 59.2

root@am62xx-evm:~#

The demonstration effect of the rgx_triangle_test command is as follows:

Our project did not use the Wayland/Houston framework or the X11 framework. The output of the eglinfo instruction is as follows:

root@am62xx-evm:~# eglinfo
EGL client extensions string:
    EGL_EXT_client_extensions EGL_EXT_device_base
    EGL_EXT_device_enumeration EGL_EXT_device_query EGL_EXT_platform_base
    EGL_KHR_client_get_all_proc_addresses EGL_KHR_debug
    EGL_EXT_platform_device EGL_EXT_platform_wayland
    EGL_KHR_platform_wayland EGL_MESA_platform_gbm EGL_KHR_platform_gbm
    EGL_MESA_platform_surfaceless

GBM platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL_ES
EGL extensions string:
    EGL_ANDROID_native_fence_sync EGL_EXT_buffer_age
    EGL_EXT_create_context_robustness EGL_EXT_image_dma_buf_import
    EGL_EXT_image_dma_buf_import_modifiers EGL_EXT_image_gl_colorspace
    EGL_EXT_yuv_surface EGL_IMG_context_priority EGL_KHR_cl_event2
    EGL_KHR_config_attribs EGL_KHR_create_context EGL_KHR_fence_sync
    EGL_KHR_get_all_proc_addresses EGL_KHR_gl_colorspace
    EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image
    EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image
    EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap
    EGL_KHR_no_config_context EGL_KHR_partial_update
    EGL_KHR_reusable_sync EGL_KHR_surfaceless_context
    EGL_EXT_pixel_format_float EGL_KHR_wait_sync
    EGL_MESA_configless_context EGL_MESA_drm_image
    EGL_MESA_image_dma_buf_export EGL_MESA_query_driver
    EGL_WL_bind_wayland_display EGL_IMG_cl_image
Configurations:
     bf lv colorbuffer dp st  ms    vis   cav bi  renderable  supported
  id sz  l  r  g  b  a th cl ns b    id   eat nd gl es es2 vg surfaces
---------------------------------------------------------------------
0x01 32  0  8  8  8  8  0  0  0 0 0x34325241--      a     y        win,pb
0x02 32  0  8  8  8  8  0  0  2 1 0x34325241--      a     y        win,pb
0x03 32  0  8  8  8  8  0  0  4 1 0x34325241--      a     y        win,pb
0x04 32  0  8  8  8  8 24  8  0 0 0x34325241--      a     y        win,pb
0x05 32  0  8  8  8  8 24  8  2 1 0x34325241--      a     y        win,pb
0x06 32  0  8  8  8  8 24  8  4 1 0x34325241--      a     y        win,pb
0x07 24  0  8  8  8  0  0  0  0 0 0x34325258--      y     y        win,pb
0x08 24  0  8  8  8  0  0  0  2 1 0x34325258--      y     y        win,pb
0x09 24  0  8  8  8  0  0  0  4 1 0x34325258--      y     y        win,pb
0x0a 24  0  8  8  8  0 24  8  0 0 0x34325258--      y     y        win,pb
0x0b 24  0  8  8  8  0 24  8  2 1 0x34325258--      y     y        win,pb
0x0c 24  0  8  8  8  0 24  8  4 1 0x34325258--      y     y        win,pb
0x0d 16  0  5  6  5  0  0  0  0 0 0x36314752--      y     y        win,pb
0x0e 16  0  5  6  5  0  0  0  2 1 0x36314752--      y     y        win,pb
0x0f 16  0  5  6  5  0  0  0  4 1 0x36314752--      y     y        win,pb
0x10 16  0  5  6  5  0 24  8  0 0 0x36314752--      y     y        win,pb
0x11 16  0  5  6  5  0 24  8  2 1 0x36314752--      y     y        win,pb
0x12 16  0  5  6  5  0 24  8  4 1 0x36314752--      y     y        win,pb

Wayland platform:
error: XDG_RUNTIME_DIR not set in the environment.
error: XDG_RUNTIME_DIR not set in the environment.
eglinfo: eglInitialize failed

Device platform:
eglinfo: eglInitialize failed

root@am62xx-evm:~#

But when we use the kmscube command, the following error occurs The error message is that EGL configurations cannot be found, but we have already ported dependency libraries such as EGL and OpenGL. And before and after executing the kmscube command, the content displayed in cat/sys/kernel/debug/pvr/status is also different.

root@am62xx-evm:~# cat /sys/kernel/debug/pvr/status
Driver Status:   OK

Device ID: 0:128
Firmware Status: OK
Server Errors:   0
WGP Error Count: 0
TRP Error Count: 0
APM Event Count: 0
root@am62xx-evm:~# kmscube -D /dev/dri/card0
[   41.577338] PVR_K:  357: RGX Firmware image 'rgx.fw.33.15.11.3' loaded
[   41.583422] PVR_K:  357: Shader binary image 'rgx.sh.33.15.11.3' loaded
Using display 0x102fbc80 with EGL version 1.5
===================================
EGL information:
  version: "1.5"
  vendor: "Mesa Project"
  client extensions: "EGL_EXT_client_extensions EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query EGL_EXT_pl                                                                      atform_base EGL_KHR_client_get_all_proc_addresses EGL_KHR_debug EGL_EXT_platform_device EGL_EXT_platform_wayland EGL_KHR_platf                                                                      orm_wayland EGL_MESA_platform_gbm EGL_KHR_platform_gbm EGL_MESA_platform_surfaceless"
  display extensions: "EGL_ANDROID_native_fence_sync EGL_EXT_buffer_age EGL_EXT_create_context_robustness EGL_EXT_image_dma_bu                                                                      f_import EGL_EXT_image_dma_buf_import_modifiers EGL_EXT_image_gl_colorspace EGL_EXT_yuv_surface EGL_IMG_context_priority EGL_K                                                                      HR_cl_event2 EGL_KHR_config_attribs EGL_KHR_create_context EGL_KHR_fence_sync EGL_KHR_get_all_proc_addresses EGL_KHR_gl_colors                                                                      pace EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image EG                                                                      L_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_no_config_context EGL_KHR_partial_update EGL_KHR_reusable_sync EGL                                                                      _KHR_surfaceless_context EGL_EXT_pixel_format_float EGL_KHR_wait_sync EGL_MESA_configless_context EGL_MESA_drm_image EGL_MESA_                                                                      image_dma_buf_export EGL_MESA_query_driver EGL_WL_bind_wayland_display EGL_IMG_cl_image "
===================================
No EGL configs with appropriate attributes.
failed to choose config
failed to initialize EGL
root@am62xx-evm:~# cat /sys/kernel/debug/pvr/status
Driver Status:   OK

Device ID: 0:128
Firmware Status: OK
Server Errors:   0
HWR Event Count: 0
CRR Event Count: 0
SLR Event Count: 0
WGP Error Count: 0
TRP Error Count: 0
FWF Event Count: 0
APM Event Count: 1
GPU Utilisation: 0%
                    VM0
2D    Utilisation:   0%
GEOM  Utilisation:   0%
3D    Utilisation:   0%
CDM   Utilisation:   0%
root@am62xx-evm:~#

After I configure the Qt environment variables, our application will also report an error saying 'cannot find egl configs':

After I configure the Qt environment variables, our application will also report an error saying 'cannot find egl configs':

I would like to ask TI, what is the reason for the error of not being able to find egl configs, and is it related to me not using the display framework (Wayland/West)? Is the inconsistency in the content viewed by cat/sys/kernel/debug/pvr/status related to the unsuccessful loading of GPU drivers? Please ask TI experts to help me take a look, thank you!

22 days ago

0 Zhang Hang 22 days ago

Prodigy 155 points

After I configure the Qt environment variables, our application will also report an error saying 'cannot find egl configs':

2018-03-21T18:29:19.886Z: Cmp=SysGraphicWindowQt, Class=2, Error=0, Info=0, pszInfo=!!!! Cannot find EGLConfig, returning null                                                                       config (:0, )
2018-03-21T18:29:19.886Z: Cmp=SysGraphicWindowQt, Class=8, Error=0, Info=0, pszInfo=#### EGL Error : Could not create the egl                                                                       surface: error = 0x3005
 (:0, )

The Qt environment variable configuration is as follows:

########################################arm64-qt########################################
export QT_ROOT=/usr/lib/arm64-qt5
export QT_QPA_GENERIC_PLUGINS=tslib:/dev/input/event0
export QT_QPA_FONTDIR=$QT_ROOT/fonts
export QT_QPA_PLATFORM_PLUGIN_PATH=$QT_ROOT/plugins/platforms
export QT_QPA_PLATFORM=eglfs
export QT_QPA_EGLFS_INTEGRATION=eglfs_gbm
export EGL_PLATFORM=gbm
export QT_QPA_EGLFS_DRM_DEVICE=/dev/dri/card0
export QT_PLUGIN_PATH=$QT_ROOT/plugins
export LD_LIBRARY_PATH=$QT_ROOT/lib:$QT_ROOT/plugins/platforms:$LD_LIBRARY_PATH
export QML2_IMPORT_PATH=$QT_ROOT/qml
export QT_QPA_FB_TSLIB=1

0 Krunal Bhargav34 21 days ago in reply to Zhang Hang

TI__Mastermind 44735 points

What behavior do you see when you use /dev/dri/card1?

Regards,
Krunal

0 Zhang Hang 21 days ago in reply to Krunal Bhargav34

Prodigy 155 points

The behavior is as bleow:

root@am62xx-evm:~# kmscube -D /dev/dri/card1
no connected connector!
failed to initialize legacy DRM
root@am62xx-evm:~#

0 Krunal Bhargav34 20 days ago in reply to Zhang Hang

TI__Mastermind 44735 points

Thanks and card0 is the right card to use. Is the above issue on your custom built SDK? Besides the Kernel module, did you pull the UM part of the driver? Please remember we have 3 drivers:
1. https://git.ti.com/cgit/arago-project/meta-ti/tree/meta-ti-bsp/recipes-graphics/powervr-umlibs/ti-img-rogue-umlibs_23.3.6512818.bb?h=kirkstone
2. https://git.ti.com/cgit/arago-project/meta-ti/tree/meta-ti-bsp/recipes-bsp/powervr-drivers/ti-img-rogue-driver_23.3.6512818.bb?h=kirkstone
3. https://git.ti.com/cgit/arago-project/meta-ti/tree/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb?h=kirkstone

Regards,

Krunal

0 Tony Tang 17 days ago in reply to Krunal Bhargav34

TI__Mastermind 29172 points

Hi Krunal,

I don't know how to use GPU, I am afraid I will describe in wrong way.

#1. Customer uses simplified tiny file system due to limited storage capacity, there is not systemd, no wayland.

#2. Customer doesn't use Wayland/wesaston, use GPU with OPENGL and EGL directly, it report EGL configs error as upper log. Do you see any wrong steps of customer's procedure?

Krunal Bhargav34 said:
1. https://git.ti.com/cgit/arago-project/meta-ti/tree/meta-ti-bsp/recipes-graphics/powervr-umlibs/ti-img-rogue-umlibs_23.3.6512818.bb?h=kirkstone
2. https://git.ti.com/cgit/arago-project/meta-ti/tree/meta-ti-bsp/recipes-bsp/powervr-drivers/ti-img-rogue-driver_23.3.6512818.bb?h=kirkstone
3. https://git.ti.com/cgit/arago-project/meta-ti/tree/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb?h=kirkstone

#3. Are these 3 URL all drivers? customer said the later 2 are libraries. customer don't know how to do with it? git it to customer's filesystem? more details would helpful.

#4. Is there a example for this customer's use case?

#5. is there a guide of how to use GPU based on TI SDK?

0 Krunal Bhargav34 16 days ago in reply to Tony Tang

TI__Mastermind 44735 points

Hi Tony,

#1: For the tiny file system, are they building it through Yocto?

#2 and #3: Understood. The tiny filesystem does not includes all the necessary libraries and I don't think loading GPU module is sufficient. They also need to copy the GPU user mode libraries. Can they share the output of "ls /usr/lib"?

#4 and #5: Typically, customers build tiny filesystem through Yocto and add GPU recipes to their configs.

Regards,
Krunal

0 Zhang Hang 16 days ago in reply to Krunal Bhargav34

Prodigy 155 points

Hi,

#1: Our file system is not building through Yocto, we are using the file system in the SDK : INSTALL_PATH/ti-processor-sdk-linux-am62xx-evm-09.02.01.10/filesystem/am62xx-evm/tisdk-tiny-initramfs-am62xx-evm.cpio

#2 and #3: The output of "ls/usr/lib" is as below:

#4 and #5: I think I should have added the relevant library to the file system. Please help to check if I missed something.

0 Zhang Hang 16 days ago in reply to Zhang Hang

Prodigy 155 points

I'm not sure if I'm missing any libraries right now. Can the TI expert help me check if any libraries are missing? If there are no missing libraries, what other reasons could have caused this issue?

0 Krunal Bhargav34 15 days ago in reply to Zhang Hang

TI__Mastermind 44735 points

Hello,

The above issue is due to missing GPU libraries. Typically, our initramfs doesn't package GPU libs because it's supposed to be a minimal file system. A few questions for you:
1. Does kmstest run successfully?
2. Add the following print to get more messages: EGL_LOG_LEVEL=debug
3. Please make sure you also build mesa using the instructions listed here: https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/11_01_05_03/exports/docs/linux/Foundational_Components/Graphics/Rogue/Build_Guide.html. The build guide shows all the various components that you need. I hope this helps.

Regards,
Krunal

Processors

Processors forum

AM625: AM6254 GPU Cannot find EGLConfig