[meta-ti] BeagleBone Black - ti-sgx-ddk not working on yocto Krogoth, what is missing
Simon Pelletier-Thibault
simon.pelletiert at gmail.com
Fri Oct 7 18:49:14 PDT 2016
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20161007/65cadc63/attachment.html>
More information about the meta-ti
mailing list