On 25/12/2009 17:54, Martin Michlmayr wrote:
* Eric Valette<eric.vale...@free.fr> [2009-12-24 18:08]:
Reading flash-kernel, I can probably rewrite it to skip the mtd check
but I would rather be sure that this will be understood by uboot
rather using kermit and uboot command rather than writing it directly
to mtd devices as it is done via a live system.
You can modify flash-kernel to write the kernel/ramdisk to a flash
rather than mtdblock. If you can wait 10 days, I can also create an
image for you.
Sure I can wait because, at least, it works now except the kernel
upgrade part.
I would be grateful if you do the work as I risk to corrupt my devices
further if I cannot manage to correctly build the kernel and ramdisk so
that they can be understood correctly by uboot. If is requires you a
good amount of work, I can propose an alternative below.
FYI: I already have a serial console, but I'm not the only user on the
planet I hope and I'm rather sure not all people have one. Just I never
managed to get into uboot with it. I understand <SPACE> and then "1" is
the correct way. Should try again as I do not remember what I did when
trying to unbrick the device because the first debian install went
wrong. I just discovered that waiting long enough with not sata disk
connected was yielding a root shell and that was sufficient to clean the
error I got during running the debian installer (I run linux debian for
about 13 years, and have unbricked many machines but not that much
embedded ones or directly via jtag)
To save you work, I propose to wait until the 2.6.32-3 kernel becomes
available and I will then try with the kermit/serial console option.
Now, to do that, there are still some bits I do not understand because
I'm not familiar with uboot and restarting from an original/debian
installer netboot.img is not an option.
What is the correct way to tranform things in /boot (e.g.
initrd.img-2.6.31-1-orion5x and vmlinuz-2.6.31-1-orion5x) into the parts
that can be understood by the uboot command interpreter like uKernel and
uRamdisk produced by the splitdns323fw in the recovery option page?
Are the devio + mkimage contained in the flash-kernel script sufficient?
If yes, why not providing an option to save those files for people
needing to do recovery (flashing the original/debian installer
netboot.img is not an interesting option for people having debian
already installed)
For kernel:
devio > "$tmp" 'wl 0xe3a01c06,4' 'wl 0xe3811006,4'
cat "$kfile" >> "$tmp"
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 \
-e 0x00008000 -n "$desc" -d "$tmp" "$tmp.uboot"
>&2 1>/dev/null
For ramdisk:
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00800000 \
-e 0x00800000 -n "$idesc" -d "$ifile"
"$tmp.uboot" >&2 1>/dev/null
And I forget yesterday because the debian Christmas present was rather
spicy: Merry Christmas.
--eric
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
