Hi all,
Are these unique to the mainboard or are they generic of the bios in this case Coreboot? I have a build of coreboot that builds and then displays a few numbers and bombs out on FF. Does anybody know that FF is stands for?
Mainboard: Sun Workstation Ultra 20 M2 (Tyan made maybe) Chipset: MCP55
Answered my own question... but leads me onto another.
The FF means 'Boot attempt (INT 19h).' which I can only assume is a good thing. I am not getting a VGA output. I am using Seabios and have included the VGABios, and used CBFSTool to package it up but still no joy. Where would be the next logical step from here?
Thanks
Dave
On Tue, Sep 29, 2009 at 4:31 PM, Crankyadmin root@crankyadmin.net wrote:
Hi all,
Are these unique to the mainboard or are they generic of the bios in this case Coreboot? I have a build of coreboot that builds and then displays a few numbers and bombs out on FF. Does anybody know that FF is stands for?
Mainboard: Sun Workstation Ultra 20 M2 (Tyan made maybe) Chipset: MCP55
Do you have any path to serial?
ron
Crankyadmin wrote:
The FF means 'Boot attempt (INT 19h).'
I don't think this is it.
I would guess that instead there is a fatal error somewhere and the last helpful value gets overwritten.
You really must get debug output in order to get help with this. We need to see the messages.
Work out how to use USB debug device on another, working, board. Possibly start with just using it for the Linux console on another board, then you don't need coreboot at first. But do validate the USB debug setup also with a known working board using coreboot, before you try to use it for the MCP55 board.
Yes, it requires some money and effort, but trying to bring up a coreboot board using nothing but POST codes is a waste of everyone's time. :\
//Peter
Recieved and understood...
On Tue, Sep 29, 2009 at 10:17 PM, Peter Stuge peter@stuge.se wrote:
Crankyadmin wrote:
The FF means 'Boot attempt (INT 19h).'
I don't think this is it.
I would guess that instead there is a fatal error somewhere and the last helpful value gets overwritten.
You really must get debug output in order to get help with this. We need to see the messages.
Work out how to use USB debug device on another, working, board. Possibly start with just using it for the Linux console on another board, then you don't need coreboot at first. But do validate the USB debug setup also with a known working board using coreboot, before you try to use it for the MCP55 board.
Yes, it requires some money and effort, but trying to bring up a coreboot board using nothing but POST codes is a waste of everyone's time. :\
//Peter
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
OK I have not had a chance to check but IIRC FF is 'died' and FE is 'I am trying to jump to the payload'.
ron
Found the Sun manual for this board... it means Boot attempt (INT 19h)
Going to leave this untill I have a sane way of debugging... should only be a week or so.
Dave
On Tue, Sep 29, 2009 at 11:26 PM, ron minnich rminnich@gmail.com wrote:
OK I have not had a chance to check but IIRC FF is 'died' and FE is 'I am trying to jump to the payload'.
ron
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
On 30.09.2009 01:06, David Houston wrote:
Found the Sun manual for this board... it means Boot attempt (INT 19h)
Please note that coreboot uses its own set of POST codes which are totally independent of the POST codes your board may originally have had. In short, ignore any manuals (because they don't apply anymore) and grep for post_code or POST_CODE in coreboot instead. No idea how SeaBIOS sends POST codes, but "grep -ir post ." in the source directory should help you find out quickly.
SeaBIOS and coreboot may have overlapping POST code ranges. There is no standard whatsoever, so every developer just picks the codes he/she likes.
Regards, Carl-Daniel
On Wed, Sep 30, 2009 at 01:17:03AM +0200, Carl-Daniel Hailfinger wrote:
Please note that coreboot uses its own set of POST codes which are totally independent of the POST codes your board may originally have had. In short, ignore any manuals (because they don't apply anymore) and grep for post_code or POST_CODE in coreboot instead. No idea how SeaBIOS sends POST codes, but "grep -ir post ." in the source directory should help you find out quickly.
SeaBIOS doesn't use POST codes at all. SeaBIOS debugging info is only available via the serial port (though adding ehci debug support would be nice).
-Kevin
On 29.09.2009 17:31, Crankyadmin wrote:
Hi all,
Are these unique to the mainboard or are they generic of the bios in this case Coreboot? I have a build of coreboot that builds and then displays a few numbers and bombs out on FF. Does anybody know that FF is stands for?
Yes, it usually means that either the code called die() due to an uncaught error or it is not finding the ELF payload. Are you using CBFS or classic ELF payload?
Regards, Carl-Daniel
Seabios with CBFS.
On Tue, Sep 29, 2009 at 4:50 PM, Carl-Daniel Hailfinger < c-d.hailfinger.devel.2006@gmx.net> wrote:
On 29.09.2009 17:31, Crankyadmin wrote:
Hi all,
Are these unique to the mainboard or are they generic of the bios in this case Coreboot? I have a build of coreboot that builds and then displays a few numbers and bombs out on FF. Does anybody know that FF is stands for?
Yes, it usually means that either the code called die() due to an uncaught error or it is not finding the ELF payload. Are you using CBFS or classic ELF payload?
Regards, Carl-Daniel
-
Carl-Daniel Hailfinger -
Crankyadmin -
David Houston
-
Kevin O'Connor -
Peter Stuge -
ron minnich