jim, have you double checked with TI folks in linaro-android channel on the exact kernel/binary version combination to use? when i talked to them they were quiet helpful. only problem was that the had not pushed the defconfig yet and that there were build failures for kernel. anyway, first step is really to make our leb-panda build use a) their proposed kernel tree/version and b) include their exact binaries. then when we have a build we can daily show we can probably get them to fix things or at least get ideas from them on what might be wrong.

at least we have then done our part of the homework.
zach, have you tried with the omapzoom.org kernel? maybe try 35 and 38 and 39 branches and see what happens. fact is that we cannot fix and debug this on our own right now, but should report our findings as bugs properly.

Am 04.05.2011 03:40 schrieb "Jim Huang" <jim.huang@linaro.org>:
> 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?
>
> 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)