On Tue, May 3, 2011 at 9:40 PM, Jim Huang jim.huang@linaro.org wrote:
On 3 May 2011 23:52, Zach Pfeffer zach.pfeffer@linaro.org wrote:
Yeah...just fought through similar issues with the DM8168.
Jim, do you have Code Composer and the JTAG or are you debugging the SGX without it?
hi Zach and Rob,
I have no tool to debug SGX, and I have no background knowledge to resolve SGX issues.
How can I do?
Not sure if there is any way to get a build w/ debug enabled for both kernel and userspace side (because again, debug is one of those options that if you enable on kernel side you have to enable on user side and visa versa)
How are you getting the userspace binaries? Are those prebuilt by someone? I'm not quite sure how it works for android, but I guess if we can track down who can provide debug binaries for userspace (BUILD=debug), then for kernel build in menuconfig go to Device Drivers -> Graphics Support -> PowerVR build type, and select 'SGX540 DEBUG'
I'm not sure JTAG would help much.. getting all the traces that are disabled at build time by default would, because this would tell you which bits in the features mask mismatch, etc.
BR, -R
Thanks, -jserv
On 3 May 2011 08:34, Clark, Rob rob@ti.com wrote:
On Mon, May 2, 2011 at 10:44 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote: > E/FramebufferNativeWindow( 2057): couldn't open framebuffer HAL (No such device)
btw, usually a failure here could be a mismatch between kernel and userspace pvr stuff.. version mismatch or configuration mismatch could cause this.. (unfortunately non debug builds have all the traces stripped out making identifying *what* is misaligned a bit tricky to identify)