[meta-ti] BeagleBone Black - ti-sgx-ddk not working on yocto Krogoth, what is missing
Simon Pelletier-Thibault
simon.pelletiert at gmail.com
Mon Oct 10 13:26:59 PDT 2016
Hi Eric, Denys
Thank you for answering.
I tried the following:
root at beaglebone:~# gles1test1
PVR:(Error): WSEGL_CreateWindowDrawable: Couldn't set CRTC: Invalid
argument [0, ]
'eglCreateWindowSurface' returned egl error 'EGL_BAD_ALLOC' (0x3003)
root at beaglebone:~# gles2test1
--------------------- started ---------------------
PVR:(Error): WSEGL_CreateWindowDrawable: Couldn't set CRTC: Invalid
argument [0, ]
'eglCreateWindowSurface' returned egl error 'EGL_BAD_ALLOC' (0x3003)
I also try other configurations, like core-image-weston. After "adjusting"
mesa so it won't install gbm, weston won't boot and I still errors.
here the weston output:
starting with no config
Loding module/usr/lib/weston/drm-backend.so
output repaint windows is 7 ms maximun
initilizing drm backend
using /dev/dri/card0
Loading module /usr/lib/weston/gl-rendered.so
...
loaded module: found gbm_pvr.so
found valid GBM backend : gbm_pvr.so
warning no EGL_EXT_platform_base support of specific platform; failling
back to eglGetDisplay
failed to choose EGL config
failed to initialize egl
fatal: failed to create compositor backend
I think the problem is around the drm thing. I'm not an expert but:
when I look at /dev/dri/*, I see 2 card ( as if there is 2 drm driver)
root at beaglebone:~# ls -lsa /dev/dri/
0 drwxr-xr-x 2 root root 120 Jan 1 1970 .
0 drwxr-xr-x 11 root root 13160 Oct 6 04:22 ..
0 crw-rw---- 1 root video 226, 0 Jan 1 1970 card0
0 crw-rw---- 1 root video 226, 1 Jan 1 1970 card1
0 crw-rw---- 1 root video 226, 64 Jan 1 1970 controlD64
0 crw-rw---- 1 root video 226, 128 Jan 1 1970 renderD128
also
root at beaglebone:~# ls -lsa /sys/class/drm/card0/device/driver
0 lrwxrwxrwx 1 root root 0 Oct 6 04:31
/sys/class/drm/card0/device/driver ->
../../../../bus/platform/drivers/tilcdc
root at beaglebone:~# ls -lsa /sys/class/drm/card1/device/driver
0 lrwxrwxrwx 1 root root 0 Oct 6 04:35
/sys/class/drm/card1/device/driver ->
../../../../bus/platform/drivers/pvrsrvkm
1. So it sound that there is 2 drm drivers is it normal?
2. Should I change the device three to remove tilcdc, so the only drm
driver will be pvrsrvkm?
3. Is there something to do to ensure libdrm use the SGX driver?
On Mon, Oct 10, 2016 at 10:27 AM, Denys Dmytriyenko <denys at ti.com> wrote:
> FYI, that is not part of meta-ti - both kmscube and SGX demos are part of
> meta-arago application layer, not meta-ti BSP layer.
>
> --
> Denys
>
>
> On Mon, Oct 10, 2016 at 02:19:22PM +0000, Ruei, Eric wrote:
> > Hi, Simon:
> >
> > Most of the SGX test programs including sgx_init_test will not work
> anymore because we have switched to DRM-based EGL Window Systems.
> > Have you tried other SGX test programs at the file system?
> >
> > - Weston?
> >
> > - QT programs ion top of Weston?
> >
> > - Without Weston
> >
> > o Kmscube
> >
> > o /usr/bin/SGX/demos/Raw/ OGLES2ChameleonMan
> >
> > o …
> >
> > Best regards,
> >
> > Eric
> > From: meta-ti-bounces at yoctoproject.org [mailto:meta-ti-bounces@
> yoctoproject.org] On Behalf Of Simon Pelletier-Thibault
> > Sent: Friday, October 07, 2016 9:49 PM
> > To: meta-ti at yoctoproject.org
> > Subject: [meta-ti] BeagleBone Black - ti-sgx-ddk not working on yocto
> Krogoth, what is missing
> >
> > Hi,
> > I'm trying to use sgx driver for EGL application on BeagleBone Black. I
> build a minimal image to test it and it is not working.
> > I got this:
> > root at beaglebone:~# sgx_init_test
> > ----------------------- Start -----------------------
> > Try calling PVRSRVConnect with an invalid argument:
> > PVR:(Error): PVRSRVConnect: Invalid connection. [0, ]
> > PVR:(Error): PVRSRVConnect: Unable to open connection. [0, ]
> > OK
> > Call PVRSRVConnect with a valid argument:
> > OK
> > Try calling PVRSRVEnumerateDevices with invalid puiNumDevices:
> > PVR:(Error): PVRSRVEnumerateDevices: Invalid params [0, ]
> > OK
> > Get number of devices from PVRSRVEnumerateDevices:
> > OK
> > .... Reported 1 devices
> > .... Device Number | Device Type
> > 0000 | PVRSRV_DEVICE_ID_SGX
> > Attempt to acquire device 0:
> > OK
> > Getting SGX Client info
> > OK
> > .... ui32ProcessID:266
> > Display Class API: enumerate devices
> > OK
> > PVRSRVEnumerateDeviceClass() returns 0 display device(s)
> > FAIL - PVRSRV_ERROR_NO_DC_DEVICES_FOUND
> > -----
> > Here my configuration:
> > bblayes.conf:
> > POKY_BBLAYERS_CONF_VERSION = "2"
> >
> > BBPATH = "${TOPDIR}"
> > BBFILES ?= ""
> >
> > BBLAYERS ?= " \
> > /path/poky2.1/meta \
> > /path/poky2.1/meta-poky \
> > /path/meta-ti2 \
> > "
> > -----
> >
> > local.conf:
> > PACKAGECONFIG_append_pn-qemu-native = " sdl"
> > PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
> > CONF_VERSION = "1"
> >
> > PREFERRED_PROVIDER_virtual/egl = "ti-sgx-ddk-um"
> > PREFERRED_PROVIDER_virtual/libgles1 = "ti-sgx-ddk-um"
> > PREFERRED_PROVIDER_virtual/libgles2 = "ti-sgx-ddk-um"
> >
> > IMAGE_INSTALL_append_pn-core-image-minimal = " packagegroup-base-vfat
> packagegroup-base-usbhost dropbear linux-firmware ti-sgx-ddk-km
> ti-sgx-ddk-um libdrm"
> >
> > -----
> > What am I missing?
> >
> > I try other configurations, like core-image-weston. After "adjusting"
> mesa so it won't install gbm, weston won't boot and I still get the
> previous error.
> > Thank you.
> > Simon
> >
>
> > --
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti at yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20161010/3248bfec/attachment.html>
More information about the meta-ti
mailing list