Re: Who's the maintainer for the freescale MPC8349ITX board?

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

quoted

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

"Russell McGuire" [off-list ref] wrote on 01/19/2007 07:06:56 PM:

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.

Russ (and anyone else who may be watching this thread),

I did finally get the 2.6.19 kernel to boot using u-boot 1.2.0/open 
firmware device tree, but I had to do some hacking on a *.dts file that 
Timur sent me.  There may also be issues with assumptions that u-boot 
makes versus the assumptions the kernel makes versus assumptions that DTC 
make.  But, I haven't had a chance to work this issue for the last few 
days and before I put out a final word I want to have all my ducks in a 
row.  I'm going to get back to this on Monday, so stand by for more 
tomorrow evening.

Bruce

"Russell McGuire" [off-list ref] wrote on 01/19/2007 07:06:56 PM:

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.

Russ,

Sorry I took so long to get back to you on this.  I've spent the last 
couple of days trying to reproduce the problems I had bringing this board 
up to see if there really were any issues in the code or if it was just me 
not knowing what the heck I was doing.  Turned out to be the latter, 
naturally.

I can't speak to the 8360, but since it's in the same family I expect the 
differences in this regard are trivial.  I did finally manage to get the 
2.6.19.1 kernel to boot on the MPC8349ITX board using u-boot 1.2.0 (I 
don't know if u-boot 1.1.6-dirty is close enough or not) and the 
mpc8349emitx.dts file in the 2.6.19.1 tree.  Some things to know however 
(which I didn't when I started :O ).  You need to use the '-f' flag with 
the DTC to force it to compile (at least I had to with the version I 
have), otherwise it will error out when it finds no 'chosen' node.  You 
don't need one, u-boot will add a 'chosen' node on the fly.  Also, you 
need to use the '-V 0x10' flag in DTC, otherwise it defaults to making a 
version 3 blob.  u-boot seems unable to parse a version 3 blob and 
therefore can't fill in the properties it needs to for the kernel to boot. 
 So, in the end my command to generate the blob file looked like this:

./dtc -I dts -O dtb -f -V 0x10 mpc8349emitx.dts > 8349.blob

This worked for me, your milage may vary.

See 'ya!

Bruce