• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 1278 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

problems with omapdss, framebuffer, manager, display etc

dj42901
Expert 1270 points
Other Parts Discussed in Thread: AM3517

I am trying to connect a new LCD to my am3517 EVM.

Following various directions, trying both bootargs and sysfs approaches.

If I don't change anything but the display, I get multiple images on the new LCD.

The LCD is a PixelQi PQ 3Qi-01, 1024x600.  Its connected through a DVI to LVDS adapter board, and that is connected to the am3517 EVM with an HDMI-DVI cable.

My latest attempt, I use these bootargs:

setenv bootargs console=ttyO2,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=192.168.1.141:/home/user/ti-sdk-am3517-evm-05.02.00.00/targetNFS,nolock, mem=256M vram=10M omapfb.vram=0:4M,1:3M,2:3M omapdss.def_disp="dvi" omapfb:mode=1024x600MR-24@60

Then after boot, I set display timing via sysfs, run fbset to set frame buffer resolution to match, and restart PVR:

echo "43970,1024/48/80/32.600/3/6/10" > /sys/devices/platform/omapdss/display2/timings
fbset -fb /dev/fb0 -xres 1024 -yres 600 -vxres 1024 -vyres 600

/etc/init.d/rc.pvr stop

/etc/init.d/rc.pvr start

 

Right after boot, I still have the 8x display of the usual small screen image.

After the command line operations, I have a blank screen.

All of this framebuffer -> manager -> overlay -> display stuff is pretty confusing to me, so I may well not understand what I am doing here.

Here is a dump of some of the DSS settings:

display0/enabled
0
display2/enabled
1
display2/name
dvi
display2/timings
43970,1024/48/80/32,600/3/6/10
display2/driver/name
generic_panel
manager0/name
lcd
manager0/display
dvi
overlay0/enabled
1
overlay0/input_size
1024,600
overlay0/name
gfx
overlay0/position
0,0
overlay0/output_size
1024,600
overlay0/manager
lcd
omapfb/graphics/fb0/overlays
0
omapfb/graphics/fb0/modes
U:1024x600p-59
U:640x480p-59
omapfb/graphics/fb0/overlays
0
omapfb/graphics/fb0/size
4194304
omapfb/graphics/fb0/name
omapfb
omapfb/graphics/fb0/virtual_size
1024,600
omapfb/graphics/fb0/dev
29:0
omapfb/graphics/fb0/modes
U:1024x600p-59
U:640x480p-59

Thanks in advance for any help or suggestions anyone can offer, I am running out of things to try.

 

 

 

  • 0
    TI__Expert 8180 points

    Have you tried configuring your Display timing directly in panel file (drivers/video/omap2/display/panel-generic.c)? When you set default display to DVI, this is the panel which gets used.

     

    Thanks

    Vaibhav

  • 0 in reply to Vaibhav Hiremath
    Expert 1270 points

    Hi Vaibhav,

     

    I was getting to the point of looking at that when I found the "spell" i needed to make it work.

    For the record, my major problem was probably that I misunderstood what the LCD panel was, it was in fact 1280x800 while I was thinking it was 1024x600.

    Given the right display resolution, now I set boot parameters:

    omapdss.def_disp="dvi" omapfb:mode=1280x800@60

    and after the boot, I do more manipulation:

    # turn off overlays for fb0 so we can fbset
    echo "" > $fb0/overlays
    fbset -fb /dev/fb0 -xres 1280 -yres 800 -vxres 1280 -vyres 800
    # set timing
    echo "68930,1280/48/80/40,800/3/3/10"  > $disp2/timings
    # reset fb0 overlay
    echo 0 > $fb0/overlays
    # re-enable overlay 0
    echo 1 > $ov0/enabled

    where $ov0, $fb0, etc have been set to the respective sysfs paths those DSS components

     

     

  • 0 in reply to dj42901
    Prodigy 180 points

    Hi 

    I am using customized AM3517 board using AM3517evm as referrence.

    i am also interfacing AUO B121EW10.V2 (1280x800) lcd with the am3517

    As vaibhav told i have gone in path  drivers/video/omap2/display/panel-generic.c

    and changed the parameters there according to my lcd, but i am not able to increase my pixel clock above 12.999 MHz,

    whatever value i give it does not increase beyond this value, please help me to know how to increase this frequency.

    I have another LCD AUO B101AW06 V.1[1024x600], on this i am able to get linux logo and test pattern also.

    But, in 1280x800 i get nothing. Please tell me a solution to this

    Best Regards

    Kshitij

  • 0 in reply to Kshitij Kumar
    TI__Expert 8180 points

    This is very strange behavior, I don't see any reason why pixel clock should not exceed beyond 12.9MHz. I have configured LCD Panel (available on AM37x EVM) to 19.2 MHz without any issues.

    Some pointers to check -

     - Can you cross check the timing parameter and DSS register configuration against what you are trying to configure?

     - Just to conform, can you use PSP03.00.01.06 release and try same panel?  There could be some issues/bug with PSP04.02.00.07 release.

    You can access the PSP03.00.01.06 release from

    http://arago-project.org/git/projects/?p=linux-omap3.git;a=shortlog;h=refs/heads/OMAPPSP_03.00.01.06

    Thanks,

    Vaibhav

  • 0 in reply to Vaibhav Hiremath
    Prodigy 180 points

    Hi Vaibhav

    Thanks for a quick reply!!

    I have commented prcm_init() in u-boot, because if i enable this my board hangs at uncompressing linux..........

    with commenting prcm_init the boot is going fine and we receive angstrom image on console

    i suspect this might be a reason i am not able to increase my pclk.

    do you also think it as a possibility??

    can you tell me why during uncompressing linux my board is getting hanged, while i am enabling prcm_init() in u-boot

    Best Regards

    Kshitij

    P.S we are doing x-load initialization in GEL files, loading u-boot through CCSv5, uImage through tftpboot and Rootfs through nfs.