Corey Osgood wrote:
On Thu, Sep 4, 2008 at 2:30 PM, Daniel Lindenaar
<[EMAIL PROTECTED]> wrote:
Corey Osgood wrote:
On Thu, Sep 4, 2008 at 11:55 AM, Daniel Lindenaar <[EMAIL PROTECTED]>
wrote:
Hi everybody,
Too bad, first test boot didn't work... at all... I expected the early
serial stuff to work at least (as this was already in svn, but...)
I'm using a very simple null-modem cable with only rx,tx and ground
wired.
Is this enough or does coreboot require a more complete cable?
Also, do I need some special settings to enable the debugging output?
I really feel like the newbie now, asking these basic questions :), but I
also would really like to get this thing working on this motherboard...
regards Daniel
Nope, that cable should be plenty, as long as it's good. A couple
things to check, when I wrote vt82c686's early serial stuff, I may
have configured it to use the second serial output, because I think
that's all my board had. I can't remember though, so check the
datasheet (I can't right now). Also, check that your debugging setup
actually works, boot linux with the stock bios and "console=tty0
console=ttyS0,115200" passed to linux. If you don't get a linux boot
log, something's wrong with your serial setup. If everything checks
out, send me a compressed copy of your tree, and I'll try to find the
problem.
-Corey
Great! the com port was indeed nr2. That works better... well the
minimal version of better actually :/
coreboot-2.0.0.0Fallback Wed Sep 3 22:07:38 UTC 2008 starting...
This is all I'm seeing... I guess I should check loglevel and such.
Corey, If you're willing to help I'll be glad to send you my tree, but I
don't want to impose too much; but if you're willing ;)
Well, serial's working now ;) Looks like you're dying either somewhere
in SMBus or ram init. I'd start with inserting LOTS of debug messages,
and turning the log level up to 9. The more messages you have, the
easier it is to pinpoint where it dies. I can try to help, but I'm not
sure how much I can ;)
-Corey
hmmm it's working partly, it seems. First i did something wrong that
skrewed up the com port setup, which I fixed. I now get the debug
messages I added via the serial line, but, strangely, only when i do a
(warm) reboot from a running linux, not with a cold boot... probably
something needs to be set that doesn't get set by default on cold reboot.
Anyway, it's the SMBus controller where things go wrong; the log says:
SMBUS controller not found
as the last item. At least some progress is made. Besides the logging
not working on cold boot, which it should at some point, I've now got
something that works well enough to start proper debugging.
regards,
Daniel
--
coreboot mailing list
[email protected]
http://www.coreboot.org/mailman/listinfo/coreboot
--
coreboot mailing list
[email protected]
http://www.coreboot.org/mailman/listinfo/coreboot
