• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 1127 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.

am335x android SGX porting problem

kadir yasar
Intellectual 730 points

Hi

I am not able to run SGX enabled Android Fs in our custom board based on am335x. We are using rowboat-jb-4.1.2. Without SGX, everythin is OK, but when i enable it after showing boot logo, nothing seems on the screen. In logcat output:

could not find an EGLConfig matching the screen format
eglQuerySurface:350 error 300d EGL_BAD_SURFACE

# cat /system/lib/egl/egl.cfg
0 0 android
0 1 POWERVR_SGX530_125
#lsmod (SGX modules are inserted succesfully)
omaplfb
pvrsrvkm
I tried SGX test tools (sgx_flip_test, sgz_init_test, ..) many of them says OK. Only texture_benchmark failed "TOO MANY BUFFERS". I searched the problem but couldnt find a solution for this android board bringup problem.
  • 0
    TI__Expert 7220 points

    Hi,

    What are the changes you have made to the display driver and the display panel platform data? Did you run all the below commands?

    insmod /system/bin/sgx/pvrsrvkm.ko
    insmod /system/bin/sgx/omaplfb.ko
    chmod 0666 /dev/pvrsrvkm
    /system/bin/pvrsrvinit

    Regards,

    Arun

  • 0 in reply to Arun Joseph
    Intellectual 730 points

    Hi Arun,

    I have no change in display driver (da8xx-fb) just i added my lcd panel info and porch values. In board file, there is straightforward change about lcd panel and it is very similar with EVM's lcd platform data. Framebuffer driver and LCD works well wtihout SGX. I cannot enable SGX support in Android boot.

    I split the Android File system 3 partitions (system, data and cache) not like in rowboat (rootfs - all in one). I tried the keep all files in same partition (rootfs) like in rowboat and boot the Android from NFS, then SGX worked. What is wrong with that ? I couldnt understand.

  • 0 in reply to kadir yasar
    TI__Intellectual 1505 points

    Hello Kadir,

            Did you mean the issue got resolved after partitioning the Android FS?

    Please share the complete logcat and dmesg logs so that it helps us to analyze the issue.

    Regards,

    Aditya

  • 0 in reply to Aditya Nellutla
    Genius 3920 points

    Hello 

               Me too have the same problem. please check this thread 

    http://e2e.ti.com/support/embedded/android/f/509/t/262876.aspx

    Thanks in advance 

  • 0 in reply to Aditya Nellutla
    Intellectual 730 points

    Hi all,

    The problem is solved when i create root file system tarball in Android build step. First i create file system tarball, i extract it and then i create two file system images (system and data) and flashed them. Then, the booting Android with SGX support from flash is successful. If i build the Android source without creating tarball and then creating filesystem images using files under out/ directory, booting with SGX support fails. I think problem is about file permissions, because Android build system change permissions of some files while creating the tarball. Without creating tarball, permissions of some files remain inconvenient for android and so in startup SGX support cannot be installed properly to system.

    In logcat output "E/SurfaceFlinger: couldn't find an EGLConfig matching the screen format" loops

    Thanks