XM start up before boot.scr

[svrsig]

If I interrupt the start up by pressing a key on the serial device, I
get the line
OMPA3 beagleboard.org #
but on the monitor it says 'out of scan 11.47kHz / 14Hz' so there
seems to be a timing issue with u-boot.bin' (an XM thing I think) that
is only sorted as the user.scr loading continues later.

[Gerald Coley]

Sounds like your monitor will not accept the default timing of the display interface as set by the uboot.bin file. I have the same exact issue on my LCD display as well. If it were correct, you would get na orange screen. Nothing else. It seems that no one can agree on what the display output resolution or timing should be because everyone has a different monitor. There is no support for the EDID interface in UBoot so the only way to set it is via a script.

 

 

Gerald

--
You received this message because you are subscribed to the Google Groups "Beagle Board" group.
To post to this group, send email to beagl...@googlegroups.com.
To unsubscribe from this group, send email to beagleboard...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.

[svrsig]

The timing registers are different on the XM to get 4x effect on
timing, I believe.

I am sure that a 14Hz frame rate is out of spec for almost every
monitor!

> > beagleboard...@googlegroups.com<beagleboard%2Bunsu...@googlegroups.com>
> > .

[Gerald Coley]

Yes. I know.

 

Gerald

 

To unsubscribe from this group, send email to beagleboard...@googlegroups.com.

[svrsig]

The issue is that if I interrupt the boot process, the default screen
mode at this point
(14Hz) is different from the default screen mode (same resolution but
60Hz) if the boot process completes into Angstom. Surely this was not
intentional?

> > <beagleboard%2Bunsu...@googlegroups.com<beagleboard%252Buns...@googlegroups.com>

[Gerald Coley]

The default mode in uBoot is an orange screen. Basically, it is useless. You cannot see any information on it. That is what the serial port is for. And yes. That was intentional. So, the fact that you see nothing on hte screen, is in essence, is no big deal. The screen is only active when you enter the kernel mode.

 

Gerald

To unsubscribe from this group, send email to beagleboard...@googlegroups.com.

[svrsig]

The only reason that I am pursuing this is that my next step is to
load riscos. The only problem is that, after it has started up, it is
producing a screen refresh rate of 15Hz rather than 60Hz (as I
understand it, it accepts the default screen settings and allows the
user to select different settings once started up - this works prior
to the XM). Is there something simple I can do at the useless orange
screen, from the serial device, to get a more sensible frame refresh
rate before doing 'fatload mmc 0 0x81000000 riscos' and 'go
0x81000000' please?

> > > > <beagleboard%2Bunsu...@googlegroups.com<beagleboard%252Buns...@googlegroups.com>
> > <beagleboard%252Buns...@googlegroups.com<beagleboard%25252Bun...@googlegroups.com>

[Jason Kridner]

On Thu, Sep 2, 2010 at 1:47 PM, svrsig <ch...@svrsig.org> wrote:
> The only reason that I am pursuing this is that my next step is to
> load riscos. The only problem is that, after it has started up, it is
> producing a screen refresh rate of 15Hz rather than 60Hz (as I
> understand it, it accepts the default screen settings and allows the
> user to select different settings once started up - this works prior
> to the XM). Is there something simple I can do at the useless orange
> screen, from the serial device, to get a more sensible frame refresh
> rate before doing 'fatload mmc 0 0x81000000 riscos' and 'go
> 0x81000000' please?

Steve Kipisz pointed out to me "On xM the parent clock is 96MHz so
96/6=16MHz, which I think you said you were seeing 15MHz. As a quick
hack I changed the PCD to 2 and now have the nice orange display on
xM."

Given that, I tried a few things:

OMAP3 beagleboard.org # md 0x48050440 0x10
48050440: 0001830b 00000004 000003ff 00ff8000 ................
48050450: 00000000 00000000 00000000 0000023d ............=...
48050460: 00000000 0ff03f31 01400504 00007028 ....1?....@.(p..
48050470: 00010006 00000000 00ef027f 02ff03ff ................
OMAP3 beagleboard.org # mw.l 0x48050440 0x00018308
OMAP3 beagleboard.org # mw.l 0x48050470 0x00010002
OMAP3 beagleboard.org # mw.l 0x48050440 0x0001830b

I did the above, but the result for me was a 34.4kHz / 43Hz signal
that my monitor still didn't recognize.

For some register information in u-boot, check out:
http://gitorious.org/beagleboard-validation/u-boot/blobs/validation-20100818/board/ti/beagle/beagle.c#line159
http://gitorious.org/beagleboard-validation/u-boot/blobs/validation-20100818/board/ti/beagle/beagle.h#line523
http://gitorious.org/beagleboard-validation/u-boot/blobs/validation-20100818/drivers/video/omap3_dss.c#line104
http://gitorious.org/beagleboard-validation/u-boot/blobs/validation-20100818/include/asm-arm/arch-omap3/dss.h#line45

> To unsubscribe from this group, send email to beagleboard...@googlegroups.com.

[Jason Kridner]

Assuming: (working with http://www.epanorama.net/faq/vga2rgb/calc.html)
Clock: 96MHz
HFP (horizontal frontporch): 36
HSW (horizontal sync): 201
HBP (backporch): 676
VFP (vertical): 5
VSW: 9
VBP: 44
H freq: 49.56kHz (1024x768 VESA = 48.36kHz)
V freq: 60Hz (matches VESA)

timing_h: 676 << 20 | 36 << 8 | 201 = 0x1A4024C9
timing_v: 44 << 20 | 5 << 8 | 9 = 0x02C00509

OMAP3 beagleboard.org # mw.l 0x48050440 0x00018308

OMAP3 beagleboard.org # mw.l 0x48050464 0x1A4024C9
OMAP3 beagleboard.org # mw.l 0x48050468 0x02C00509

OMAP3 beagleboard.org # mw.l 0x48050470 0x00010002
OMAP3 beagleboard.org # mw.l 0x48050440 0x0001830b

Orange screen lives!

[svrsig]

Getting there but it produces 'out of scan 28.5kHz / 34 Hz' on my
monitor, a Sony SDM-M61
so the calculations must be flawed. Understanding this may be
important for getting riscos to work (not just to see an orange
screen!).

Any ideas please?

On Sep 7, 10:36 pm, Jason Kridner <jkrid...@beagleboard.org> wrote:

> >http://gitorious.org/beagleboard-validation/u-boot/blobs/validation-2...
> >http://gitorious.org/beagleboard-validation/u-boot/blobs/validation-2...
> >http://gitorious.org/beagleboard-validation/u-boot/blobs/validation-2...
> >http://gitorious.org/beagleboard-validation/u-boot/blobs/validation-2...
>
> Assuming: (working withhttp://www.epanorama.net/faq/vga2rgb/calc.html)

[svrsig]

Is the video clock 96MHz or 54MHz please?

[Jason Kridner]

On Fri, Sep 10, 2010 at 6:15 AM, svrsig <ch...@svrsig.org> wrote:
> Is the video clock 96MHz or 54MHz please?

Please read up on the negatives of "top posting" for future queries.

As far as I know on the 201008201549 image's u-boot, it is 96MHz and
the commands I provided work to get a 60Hz refresh rate. Actually,
looking down at them it seems there must have a cut-and-paste error.

>>
>> > OMAP3 beagleboard.org # mw.l 0x48050440 0x00018308
>> > OMAP3 beagleboard.org # mw.l 0x48050464 0x1A4024C9
>> > OMAP3 beagleboard.org # mw.l 0x48050468 0x02C00509
>> > OMAP3 beagleboard.org # mw.l 0x48050470 0x00010002

This should have been:
OMAP3 beagleboard.org # mw.l 0x48050470 0x00010001

[trevj]

On Sep 10, 12:15 pm, Jason Kridner <jkrid...@beagleboard.org> wrote:
>
> Please read up on the negatives of "top posting" for future queries.

Easily overlooked, I'm sure... and it would appear there's another
contributor to this thread who's also forgotten (naming no names!)

[snip]

> This should have been:
> OMAP3 beagleboard.org # mw.l 0x48050470 0x00010001

Thanks for the correction. I'm confident that the RISC OS brains will
get to the bottom of this, with the continued support of you
beagleboard.org folk :-)

[svrsig]

I think the uboot uses the DPLL4 clock (54MHz) not theDSI PLL clock
(96MHz) - does this account for it?