Cubox - wrong lcd frequency range at boot

This forum is for supported devices using an ARMv7 Texas Instruments (TI) SoC.

Cubox - wrong lcd frequency range at boot

Postby kirgog » Sat Jun 09, 2012 1:44 pm

Hi all,

I'm just receiving my cubox and It's a really nice product.
I want to try archlinux but I'm encountering a problem : lcd display are out of range (vertical = 120Hz / horizontal = 90KHz)

I'm using official rootfs : http://archlinuxarm.org/platforms/armv7/cubox

I tried to modify resolution on boot.scr but same problem.
I tried to use kernel 2.6.32.9 (worked perfectly with debian) : same problem.

So I guess frequency were hardcoded with kernel compilation. I dont know.

Here is my boot.scr (tried on differend lcd / tv which support 1920x1080) :
$this->bbcode_second_pass_code('', 'setenv bootargs 'console=ttyS0,115200n8 vmalloc=384M root=/dev/mmcblk0p1 video=dovefb:lcd0:1920x1080-16@60-edid clcd.lcd0_enable=1 clcd.lcd1_enable=0'
ext2load mmc 0:1 0x00200000 /boot/uImage
bootm')

Here is /proc/mv_lcd0 :
$this->bbcode_second_pass_code('', 'Inside LCD0
Physical addr: 0xf1820000
Virtual addr: 0xfe620000
Resolution is: <1920x1080>
----total--------------------------<2200x1125>-------------------------
----active--------------|->front porch(88)->hsync(44)->back porch(148)
| |
| |
| <1920x1080> |
| |
| |
------------------------|
|
|front porch(4)
|vsync(5)
|back porch(36)
---------------------------------------------------------------------
gfx line pitch in memory is <3840>
Scaled from <1920x1080> to <1920x1080>
============================================
')

And here is my dmesg :
$this->bbcode_second_pass_code('', 'Dove FB driver:
Initialize /proc/mv_lcd0
use cat /proc/mv_lcd0 to see reg settings
dovefb dovefb.0: use ref clock SILAB_CLK0
o Kernel parameter: 1920x1080-16@60.
o Failed to read EDID information,using driver resolutions table.
found <1920x1080@60>, pixclock=6734
Found clk (requested 148500148, found 148500000)
Setting HDMI TX resolution to 1920x1080p @ 60
HDMI TX - FOUND exact resolution 16
YC pitch is 0.User program needs refine
Found clk (requested 148500148, found 148500000)
Setting HDMI TX resolution to 1920x1080p @ 60
HDMI TX - FOUND exact resolution 16
Console: switching to colour frame buffer device 240x67
o dovefb: frame buffer device was successfully loaded.')

You can see frequency are wrong : front porch(88)->hsync(44)->back porch(148)

Any idea ? Can I force it in boot.scr ? Is it a kernel setting ?
An other friend has the same problem with the same rootfs and kernel (Linux alarm 3.4.0-1-ARCH+ #1 PREEMPT Tue Jun 5 17:21:42 UTC 2012 armv7l GNU/Linux)

Thanks and regards.
Kirgog
kirgog
 
Posts: 3
Joined: Sat Jun 09, 2012 1:27 pm

Re: Cubox - wrong lcd frequency range at boot

Postby kirgog » Sat Jun 09, 2012 5:18 pm

I think It's not a kernel problem, as it's not working with 2.9.32's kernel.
Maybe it's just EDID which cannot read ldc information.
But I don't find any edid package :(
kirgog
 
Posts: 3
Joined: Sat Jun 09, 2012 1:27 pm

Re: Cubox - wrong lcd frequency range at boot

Postby pepedog » Sat Jun 09, 2012 5:42 pm

Possibly it's a setting in /etc/inittab. I thought edit was in kernel
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Cubox - wrong lcd frequency range at boot

Postby kirgog » Sat Jun 09, 2012 8:36 pm

I think inittab is OK :
$this->bbcode_second_pass_quote('', 'i')d:3:initdefault:


I can access console with ttyUSB0 and ssh.
That's just the lcd frequency which is causing trouble.
kirgog
 
Posts: 3
Joined: Sat Jun 09, 2012 1:27 pm

Re: Cubox - wrong lcd frequency range at boot

Postby jttj » Mon Jun 25, 2012 9:54 pm

kirgog, did you try setting boot.scr to 1280x720? I had the exact same problem with 1080, but 720 works for me, even though my screen supports both.
jttj
 
Posts: 7
Joined: Mon Jun 25, 2012 9:39 pm


Return to Texas Instruments (TI)

Who is online

Users browsing this forum: No registered users and 8 guests