[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Net booting iop32x with RedBoot

> There's no header usefull to RedBoot in all theses files. One needs to
> add more parameters. For instance :
> load -v -r -b 0x01800000 -m tftp /initrd.gz
> load -v -r -b 0x01008000 -m tftp /vmlinuz-2.6.30-2-iop32x
> For details about the parameters, see :
> http://ecos.sourceware.org/docs-latest/redboot/download-command.html
> Once you've looked at that and loaded initrd/kernel, use the exec
> command to boot your system.

Ok, I'm loading the kernel and initrd into place (using the addresses
from "fis list" since I don't have any boot logs), and I'm running
exec similarly to how it was run by the boot script already in the
flash.  I get the line Uncompressing Linux...., and then I don't see
anything else.  I assume at that point it's picking up a console from
some incorrect device, and I don't know what device to tell it to use.
 My session looks like this (leaving out the initrd until I can
actually get a kernel loading):

RedBoot> load -r -v -b 0x00180000 vmlinuz-2.6.30-2-iop32x
Using default protocol (TFTP)
Raw file loaded 0x00180000-0x002d95f7, assumed entry at 0x00180000
RedBoot> exec -b 0x00180000 -l 0x1595f8 -c "console=ttyS0,115200n8"
The boot tags are located at 0xA0000100
Booting the kernel...
Uncompressing Linux.............................................................

I've tried console=ttyS0 and ttyS1; either way I just get the
Uncompressing line and then nothing else.  Is is possible that the
kernel I downloaded doesn't have serial console support, or am I
missing some option to force it to use it?  Or could there be
something else that I'm doing wrong?

Reply to: