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.

Linux/AM3352: AM3352 SGX work-around

Part Number: AM3352
Other Parts Discussed in Thread: AM3358, AM3354, AM3359

Tool/software: Linux

Hello,

Does anyone know of a software work-around on Linux for the lack of an SGX graphic accelerator on the am335x processors that are missing it, specifically the am3352?

My current situation is that I'm trying to build a boo2qt image with the Yocto project for a custom board, where the designers chose to use the am3352 instead of the am3354, am3358, or am3359. I built my image using ti-sgx-ddk-um for virtual/egl, virtual/libgles1, and virtual/libgles2 knowing that it probably wasn't going to work and got the drm and pvr errors below:

[   14.015412] [drm] Initialized
[   14.733617] pvrsrvkm: loading out-of-tree module taints kernel.
[   14.797639] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   14.804385] [drm] No driver support for vblank timestamp query.
[   15.258383] tilcdc 4830e000.lcdc: fb0:  frame buffer device
[   17.132537] omap_hwmod: gfx: failed to hardreset
[   17.137344] pvrsrvkm 56000000.sgx: Unable to reset SGX!
[   17.317910] omap_hwmod: gfx: _wait_target_ready failed: -16
[   17.323683] pvrsrvkm 56000000.sgx: use pm_runtime_put_sync_suspend() in driver?
[   17.331071] PVR_K:(Error): EnableSGXClocks: pm_runtime_get_sync failed (16)
[   17.338093] PVR_K:(Error): SysInitialise: Failed to Enable system clocks (175)

To state my previous question with more of a context to my situation, what are the alternatives to ti-sgx-ddk-um that would be used for virtual/egl, virtual/libgles1, and virtual/libgles2? Mesa?

A few weeks ago I was able to get core-image-sato working on my board with the linux-yocto-4.9 kernel and no sgx, so I know this is possible. I'm really looking for suggestions that others have found to work best for the am3352.

For anyone who is curious, here' my build configuration (bei7 is my board and it's associated meta layer):

Build Configuration:
BB_VERSION        = "1.32.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal-4.8"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "bei7"
DISTRO            = "b2qt"
DISTRO_VERSION    = "2.2.1"
TUNE_FEATURES     = "arm armv7a vfp thumb neon       callconvention-hard"
TARGET_FPU        = "hard"
SDKMACHINE        = "x86_64"
meta              
meta-poky         = "morty:924e576b8930fd2268d85f0b151e5f68a3c2afce"
meta-ti           = "morty-next:ca209d8cabcdb21f58cb348e0ffb70703d61af61"
meta-freescale    = "morty:fc804d29ee85d58e9bb66f7319e749b53e192457"
meta-bei7         = "morty:924e576b8930fd2268d85f0b151e5f68a3c2afce"
meta-oe           
meta-python       
meta-networking   
meta-initramfs    
meta-multimedia   = "morty-next:fe5c83312de11e80b85680ef237f8acb04b4b26e"
meta-boot2qt      
meta-ti-extras    = "dev:5ea1d03935da72460401ec000a8be0334100d19e"
meta-mingw        = "morty:58dda8440c1943c15ee750eb40f0fc651e316f51"
meta-qt5          = "master:ff073f04109900fc07bf81e2f1df63c626caf342"

Thank you in advance for your help and please, ask me any clarifying questions you may have.