1280x1024@60 Resolution - Anybody running this?

Is anybody running 1280x1024@60 resolution on the Beagleboard XM?

I know this is overclocking and out of spec but will be interesting to
have a play with this resolution and hear comments from anybody that
has already done this.

I have a number of boards and don't mind if I blow one up pushing it
to the limits :slight_smile:

Thanks

John

Why do you say that?

I use this resolution on a BeagleBoard RevC3 with 2 DVI monitors:

  • Samsung 710T (17")
  • Dell 1908FPc (19")

No issues, working fine.
I don’t think you can fry the BB or the monitor trying this resolution. The worst thing that happens is the monitor doesn’t like the (tight) timing generated by the BB and doesn’t display any image. If your monitor supports lower refresh rates than 60Hz, and you can live with it, you can do even higher resolutions.

Regards,
Gyorgy

This is a very common resolution. Been running it myself several years since I got
my BB rev C2. No strain on the BeagleBoard at all.

djlewis

You can run this resolution in Angstrom, I actually trade to change
the u-boot.bin dvimode=640x480MR-16@60 to dvimode=1280x1024MR-16@60,
but boot fail, where I can found a u-boot.bin functional with this
resolution?

Thanks for all.

Andres

Thanks for the replies guys,

Has anybody done this on the new XM model, I am still investigaing the
differences between the XM board and earler models

Regards,

John

Thanks for the replies guys,

Has anybody done this on the new XM model, I am still investigaing the
differences between the XM board and earler models

Just the same as before, the xM is just a faster version of the old beagle with a usb hub soldered on.

We have 3 sets XM model and a Dell 2011H LCD, I want to do this testing also.

Could you please tell me how to change the resolution?

I'm a new guy for XM, I check the Angstorm wiki, but can't find the
source code.

Thanks.

Jack

Hi Koen,

Because a contact at TI said that the DM3730 video output pixel clock
max in spec is 75MHz. To support 1280x1024 60Hz refresh ratio, 1280 x
1024 x 60 x 1.2 (black pixels by vesa standard) ~= 94MHz

The Beagle Board xM could show 1280x1024 output with 60Hz but please
note that it is overclocking and out of spec. This means TI does not
guarantee it. The maximum spec in spec would be 1280 x 800 60Hz.

Koen, have you tried 1280x1024@60 on the XM model, I see from your
posts that you have a lot of experience with the Beagleboard :slight_smile:

Regards,

John

Sort of, you can mux the DSS pins to different balls on the BGA, xM is using the fast ones, so it's just like the old beagles.

regards,

Koen

>>> Is anybody running 1280x1024@60 resolution on the Beagleboard XM?

>>> I know this is overclocking and out of spec

>> Why do you say that?

> Hi Koen,

> Because a contact at TI said that the DM3730 video output pixel clock
> max in spec is 75MHz.

Sort of, you can mux the DSS pins to different balls on the BGA, xM is using the fast ones, so it's just like the old beagles.

Thanks for the reply Koen, could you post or provide a link to your
xorg.conf file for 1280x1024@60 ?

Regards,

John

I can run dvimode=1280x1024MR-16@60 in the script, I use the script
from the DVSDK linux image from
http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_4_00/latest/index_FDS.html

but like say john
" The Beagle Board xM could show 1280x1024 output with 60Hz but please
note that it is overclocking and out of spec. This means TI does not
guarantee it. The maximum spec in spec would be 1280 x 800 60Hz."

But same problem when I trade to chanche this parameter but boot fail.

Well, you set the resolution in a boot.scr on the vfat partition, just add

setenv dvimode '1280x1024MR-24@60'

Attached is a ready to go version, but you need to rename it, gmail blocks .scr files.

regards,

Koen

boot.scr.rename (218 Bytes)

Hi,
Resolution is not set by the X server. The easiest way is to pass the right omapfb parameters to the kernel in uboot:
omapfb.mode=dvi:1280x1024MR-16 omapdss.def_disp=dvi

IIRC, you can also set resolution runtime with the omapfb/omapdss sysfs framework.

Regards,
Gyorgy

Again, where do you get the idea that is it "out of spec" and "overclocking"? The supported pixclock is >170MHz on beagle

Quoting Koen Kooi <koen@beagleboard.org>:

The supported pixclock is >170MHz on beagle

Where is this specified?

I have always understood that the maximum pixel rate was
83 MHz (original BB).

Dave

Quoting Koen Kooi <koen@beagleboard.org>:

The supported pixclock is >170MHz on beagle

Where is this specified?

In the omap3 TRM.

I have always understood that the maximum pixel rate was
83 MHz (original BB).

If you use the DSI PLL you get a 173MHz pixclock. Angstrom enabled that as default in the kernel, and has done that for years now. I have 1080p24 working nicely on a C4.

Quoting Koen Kooi <koen@beagleboard.org>:

> Quoting Koen Kooi <koen@beagleboard.org>:
>
>> The supported pixclock is >170MHz on beagle
>
> Where is this specified?

In the omap3 TRM.

> I have always understood that the maximum pixel rate was
> 83 MHz (original BB).

If you use the DSI PLL you get a 173MHz pixclock. Angstrom enabled that as
default in the kernel, and has done that for years now. I have 1080p24
working nicely on a C4.

But 1920 x 1080 x 24 fps is a net rate of 48384000 triads/sec,
isn't it, so even when overheaded for the flyback periods,
it only requires a pixel clock in the ballpark of 50 MHz,
doesn't it?

Dave

72.something if I recall the hdmi specs correctly. The problem on omap3 is the the dividers you need to get a certain pixclock, using the 86.5 pixclock you will fail to get close to that

Great!

Thanks Koen,

Regards,

John