HamsterHunter HamsterHunter

Connecting a different LVDS panel to the imx53 QSB

Discussion created by HamsterHunter HamsterHunter on Apr 25, 2012
Latest reply on Mar 23, 2013 by Yahia Allam

Hi,

I need some guidance as to where to do all the changes required to make a different display work.

This is what I have: imx53 QSB with MCIMX-LVDS1 from Freescale, running the Android bsp from Adeneo. This all works fine.

What I want to do: Connect a 10.1 touch panel from "TouchRevolution" to the quick start board.The name of the display is "Fusion 10". It comes with a WSVGA resolution (1024x600). I got all the timing parameters from the manufacturer.

What I did so far:

- I build a custom cable to adapt the display to the board.

- I added the display info to the  file: ../android/i.MX53-QSB-Android-Gingerbread-Release4.2/src/kernel_imx/arch/arm/mach-mx5/mx53_loco.c :

static struct fb_videomode video_modes[] = {
     ...
     {
         .name = "WSVGA",
         .refresh = 60,
         .xres = 1024,
         .yres = 600,
         .pixclock = 48000,
         .left_margin = 104,
         .right_margin = 43,
         .upper_margin = 24,
         .lower_margin = 20,
         .hsync_len = 5,
         .vsync_len = 5,
         .sync = 0,
         .vmode = FB_VMODE_NONINTERLACED,
         .flag = 0,
    },

    ...

}

static struct mxc_fb_platform_data fb_data[] = {
   
              ...
       {
         .interface_pix_fmt = IPU_PIX_FMT_RGB666,
         .mode_str = "WSVGA",
         .mode = video_modes,
        .num_modes = ARRAY_SIZE(video_modes),
       },
       {
        .interface_pix_fmt = IPU_PIX_FMT_LVDS666,
        .mode_str = "WSVGA",
        .mode = video_modes,
        .num_modes = ARRAY_SIZE(video_modes),
      },

            ....
};

 

- Changed the bootargs to :

   U-Boot> setenv lvds 'setenv bootargs ${bootargs}
   video=mxcdi0fb:RGB666,WSVGA ldb=di0 di0_primary'
   U-Boot> setenv set_display ‘run lvds’
   U-Boot> save

 

The LCD backlight turns on but the display just stays black. I can't rule out the cable being a problem but I'm rather guessing it's something in the drivers I'm missing.

Can someone please shed some light on to what changes are required to make this work?

 

Thanks a lot!

Outcomes