LCD Render Problems with OMAP3

Hi reyes,

Could you try to capture frame buffer using DDMS and see if images is clear or noisy ?

It will give us idea whether problem lies with android layer or problem with lcd controller driver or may be loss connection with hardware.

-

satish

Hi Satish,

Thanks for your reply. The screen capture from DDMS seems clear to me, attached is the picture of the screen, I have tried to get some of the gralloc logs, but I've had no luck with that, I guess is because the library gralloc.omap.so? I traced the framebuffer values one layer above that in DisplayHardware (SurfaceFlinger).

I am using Android 2.3 from TI website: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/TI_Android_GingerBread_2_3_DevKit_1_0/index_FDS.html

Here are some lines:

01-01 00:00:07.109: INFO/SurfaceFlinger(986): SurfaceFlinger is starting

01-01 00:00:07.109: INFO/SurfaceFlinger(986): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...

01-01 00:00:07.125: ERROR/FramebufferNativeWindow(986): FramebufferNativeWindow :: GRalloc HW Module 

01-01 00:00:07.140: ERROR/FramebufferNativeWindow(986): fbDev->width :: 320, fbDev->height:: 240, fbDev->format: 4

01-01 00:00:07.140: WARN/SurfaceFlinger(986): DisplayHardware:: Init 

01-01 00:00:07.148: ERROR/libagl(986): Display eglGetDisplay return EGL_DEFAULT_DISPLAY

Problem solved...missing configuration parameters in driver:

dssdev->panel.config = OMAP_DSS_LCD_TFT | OMAP_DSS_LCD_IVS | OMAP_DSS_LCD_IHS;OMAP_DSS_LCD_TFT

Thanks for your help!

Regards