From: "Russell McGuire" <rmcguire@uwbt.com>
To: <linuxppc-embedded@ozlabs.org>
Cc: Bruce_Leonard@selinc.com
Subject: Re: Who's the maintainer for the freescale MPC8349ITX board?
Date: Fri, 19 Jan 2007 19:06:56 -0800 [thread overview]
Message-ID: <000001c73c40$0cbaf120$6405a8c0@absolut> (raw)
In-Reply-To: <mailman.1.1169168402.24872.linuxppc-embedded@ozlabs.org>
Bruce,
Did you ever get linux to boot up?
I am wondering if I am having similar problems on my system, though it is
based on the MPC8360E. Serial port code and clocking is the same between
these systems, at least it should be.
I am using Linux 2.6.19.2, and U-boot 1.1.6-dirty, though I think it
'mostly' U-boot 1.2.0 equivalent code, as 1.2.0 was released about a day
after I downloaded it.
I also can generate a 8360.blob file, and when I attempt to boot into the
kernel, it hangs with ZERO serial output, even though early serial is
defined.
-Russ
> > Per Grant's suggestion I changed it to:
> > 'dtc -I dts -O dtb -V 0x10 mpc8349emitx.dts > 8349.blob'
> >
> I get a 0 length 8349.blob file using the above. Have you tried -f?
>
> Kim
Hummmmm, interesting. I get a blob of about 4K when I do it. Oh, ooops.
Sorry. I did have to modify the *.dts file to get it to compile. There
was an error because there wasn't a 'linux,boot-cpu' entry in the cpu
node.
Adding the '-V 0x10' changed the behavior and I now seem to be hanging in
__delay() in serial8250_console_putchar(). Seems maybe the kernel is (at
least partially) up but I've got no console port. There may have been a
version issue. The DTC I'm using defaluted to a version 3 of the device
tree. I think I'm getting further in the kernel booting process (haven't
had a chance to really debug it yet) than I was now that I'm telling DCT
to generate a version 0x10 device tree.
I'm thinking this is a u-boot/*.dts file problem. The *.dts files isn't
complete and/or u-boot 1.1.6. isn't finishing filling in the device tree
as expected. I think now my problem is that the *.dts file expects u-boot
to fill in the 'clock-frequency' node in the serial ports and it's not
doing so. Timur indicates 1.1.6 doesn't support this board and I should
move to 1.2. Kumar also suggested this (even though I thought he was
suggesting I go backwards ;) sorry for the confusion Kumar) so I think
I'll give it a try. I appreciate all the help from here, but since it
seems more u-boot-ish than kernel I'm going to switch this to the u-boot
list. Seems more appropriate. If I find there are problems with the
*.dts file, I'll push that back here since they're part of the kernel
tree.
Thanks again for the help.
Bruce
next parent reply other threads:[~2007-01-20 3:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1169168402.24872.linuxppc-embedded@ozlabs.org>
2007-01-20 3:06 ` Russell McGuire [this message]
2007-01-22 3:12 ` Who's the maintainer for the freescale MPC8349ITX board? Bruce_Leonard
2007-01-24 8:15 ` Bruce_Leonard
2007-01-17 6:27 Bruce_Leonard
2007-01-17 15:42 ` Kumar Gala
2007-01-18 3:55 ` Bruce_Leonard
2007-01-18 4:23 ` Kumar Gala
2007-01-18 18:33 ` Bruce_Leonard
2007-01-18 18:40 ` Kim Phillips
2007-01-18 22:17 ` Bruce_Leonard
2007-01-19 15:06 ` Grant Likely
2007-01-18 6:20 ` Grant Likely
2007-01-18 20:02 ` Timur Tabi
2007-01-22 21:05 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000001c73c40$0cbaf120$6405a8c0@absolut' \
--to=rmcguire@uwbt.com \
--cc=Bruce_Leonard@selinc.com \
--cc=linuxppc-embedded@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).