Nitrogen6X with Vivante : restart on Qt5 examples
Hi,
I am currently trying OpenGL with Vivante driver on a Nitrogen6X using Buildroot.
Previously, I got an segfault error while starting X. "Segmentation fault at address 0xe0"
Thanks to Gary Bisson (in cc), using the galcore module from Buildroot (BR2_PACKAGE_KERNEL_MODULE_IMX_GPU_VIV=y) and not the kernel one + updating the kernel to 3.14.28, solved the issue.
With the galcore driver loaded using insmod, the Vivante is, now, working.
I compiled Qt5 examples (BR2_PACKAGE_QT5BASE_EXAMPLES=y) and I tested some openGL examples :
- "qopenglwindow" : This example is working fine
- "textures" example : in many case, the board restarts when the
application is launched.
- "hellogl" : I see the Qt logo from the example but when I try to
move the object, the board restarts.
Here is my Xorg.log, in case it could help :
http://paste.debian.net/hidden/609ae872/
Each time the board reboots, I get an "POR" reset cause in UBoot.
Maybe, I have a misconfiguration or I am doing something wrong. Any help would be great !
Thank you in advance,
Best regards
Signature · 3 lines
Myl?ne Josserand, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
Mylene, All,
Quoted 5 lines · Mylene Josserand
Hi,
I am currently trying OpenGL with Vivante driver on a Nitrogen6X using Buildroot.
Can you specify which version of Buildroot? v2016.02 or master or older?
This will help a lot to know the version of Qt, X11 etc...
Quoted 8 lines
Previously, I got an segfault error while starting X. "Segmentation fault at address
0xe0"Thanks to Gary Bisson (in cc), using the galcore module from Buildroot (BR2_PACKAGE_KERNEL_MODULE_IMX_GPU_VIV=y) and not the kernel one + updating the kernel to 3.14.28, solved the issue.
With the galcore driver loaded using insmod, the Vivante is, now, working.
Same here, please specify the exact Vivante libraries version (5.0.11p6.3 or 7.1).
Quoted 10 lines
I compiled Qt5 examples (BR2_PACKAGE_QT5BASE_EXAMPLES=y) and I tested some openGL examples :
- "qopenglwindow" : This example is working fine
- "textures" example : in many case, the board restarts when the
application is launched.
- "hellogl" : I see the Qt logo from the example but when I try to move
the object, the board restarts.Here is my Xorg.log, in case it could help :
http://paste.debian.net/hidden/609ae872/
Can you share you xorg.conf? Also specify your setup, how many displays connected, which port (HDMI, LVDS, RGB etc..).
Quoted 1 line
Each time the board reboots, I get an "POR" reset cause in UBoot.
Well then it's a feature, the Qt app appears to be restarting the board properly ;-)
Quoted 2 lines
Maybe, I have a misconfiguration or I am doing something wrong. Any help would be great !
This might sound strange, but please also provide the U-Boot version you are using. The reason is that we offer a wide range of displays, since we want customers to have a plug and play experience we've added something for kernel >=3.14 where U-Boot is in charge of modifying the device tree on the fly to setup the displays properly.
Finally, can you upload your image for me to try?
Thanks,
Gary
Gary,
Thank you for your help.
Quoted 7 lines · Gary Bisson
Mylene, All,
Quoted 3 lines · Mylene Josserand
Hi,
Quoted 6 lines
Quoted 2 lines
I am currently trying OpenGL with Vivante driver on a Nitrogen6X using Buildroot.
Can you specify which version of Buildroot? v2016.02 or master or older?
This will help a lot to know the version of Qt, X11 etc...
Yes, sorry to forget this information.
I am currently on 2016.02-rc2. I will update to v2016.02 soon. If it could help you, I can update it right now.
Quoted 11 lines
Quoted 8 lines
Previously, I got an segfault error while starting X. "Segmentation fault at address
0xe0"Thanks to Gary Bisson (in cc), using the galcore module from Buildroot (BR2_PACKAGE_KERNEL_MODULE_IMX_GPU_VIV=y) and not the kernel one + updating the kernel to 3.14.28, solved the issue.
With the galcore driver loaded using insmod, the Vivante is, now, working.
Same here, please specify the exact Vivante libraries version (5.0.11p6.3 or 7.1).
Vivante libraries : version 5.0.11.p7.1
Quoted 9 lines
Quoted 9 lines
I compiled Qt5 examples (BR2_PACKAGE_QT5BASE_EXAMPLES=y) and I tested some openGL examples :
- "qopenglwindow" : This example is working fine
- "textures" example : in many case, the board restarts when the
application is launched.
- "hellogl" : I see the Qt logo from the example but when I try to move
the object, the board restarts.
Quoted 5 lines
Quoted 2 lines
Here is my Xorg.log, in case it could help :
http://paste.debian.net/hidden/609ae872/Can you share you xorg.conf? Also specify your setup, how many displays connected, which port (HDMI, LVDS, RGB etc..).
Here is my Xorg.conf :
Section "Device"
Identifier "i.MX Accelerated Framebuffer Device"
Driver "vivante"
Option "fbdev" "/dev/fb0"
Option "vivante_fbdev" "/dev/fb0"
Option "HWcursor" "false"EndSection
Section "ServerFlags"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
EndSection
I have one HDMI display (1208x720 66Hz).
Quoted 6 lines
Quoted 2 lines
Each time the board reboots, I get an "POR" reset cause in UBoot.
Well then it's a feature, the Qt app appears to be restarting the board properly ;-)
Quoted 8 lines
Quoted 2 lines
Maybe, I have a misconfiguration or I am doing something wrong. Any help would be great !
This might sound strange, but please also provide the U-Boot version you are using. The reason is that we offer a wide range of displays, since we want customers to have a plug and play experience we've added something for kernel >=3.14 where U-Boot is in charge of modifying the device tree on the fly to setup the displays properly.
Interesting, my uboot version is : U-Boot 2013.07.
Quoted 1 line
Finally, can you upload your image for me to try?
Yes, images are coming :)
Signature · 3 lines
Myl?ne Josserand, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
Mylene, All,
Quoted 8 lines · Mylene Josserand
<snip>
Quoted 5 lines
This might sound strange, but please also provide the U-Boot version you are using. The reason is that we offer a wide range of displays, since we want customers to have a plug and play experience we've added something for kernel >=3.14 where U-Boot is in charge of modifying the device tree on the fly to setup the displays properly.
Interesting, my uboot version is : U-Boot 2013.07.
Please update, you should use either v2015.07 or v2016.03.
You should be able to just run:
U-Boot> run upgradeu
In case it doesn't work, you should fine everything you need here:
https://boundarydevices.com/compiling-latest-u-boot-for-i-mx6-2015-edition/
https://boundarydevices.com/u-boot-v2016-03/
Please make sure to clear your U-Boot environment once updated.
Thanks,
Gary