Re: Upgrading u-boot on Dreamplug
On 06/12/2013 09:27 AM, Martin Michlmayr wrote:
* Philippe Clérié <philippe@gcal.net> [2013-06-12 08:48]:
Thanks. I tried loading at 0x0080 0x0110 with the following error:
Wrong Ramdisk Image format
Ramdisk image is corrupt or invalid.
Can you post the full boot log?
I re-downloaded the images and tried again. This time I get the same as
the previous kernel. Below is the log.
U-Boot 2013.01.01 (May 10 2013 - 06:32:54)
Marvell-DreamPlug
SoC: Kirkwood 88F6281_A1
DRAM: 512 MiB
WARNING: Caches not enabled
SF: Detected MX25L1605D with page size 64 KiB, total 2 MiB
In: serial
Out: serial
Err: serial
Net: egiga0, egiga1
88E1116 Initialized on egiga0
88E1116 Initialized on egiga1
Hit any key to stop autoboot: 0
Marvell>> usb start
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 5 USB Device(s) found
scanning usb for storage devices... Device NOT ready
Request Sense returned 02 3A 00
3 Storage Device(s) found
Marvell>> fatload usb 2:1 0x00800000 uImage
reading uImage
1607552 bytes read in 128 ms (12 MiB/s)
Marvell>> fatload usb 2:1 0x01100000 uInitrd
reading uInitrd
4853363 bytes read in 254 ms (18.2 MiB/s)
Marvell>> setenv bootargs console=/dev/ttyS0,115200n8
base-installer/initramfs-tools/driver-policy=most
Marvell>> bootm 0x00800000 0x01100000
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Debian kernel
Created: 2013-05-01 8:22:14 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1607488 Bytes = 1.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: debian-installer ramdisk
Created: 2013-05-01 8:22:13 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 4853299 Bytes = 4.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
--
Philippe
------
The trouble with common sense it that it is so uncommon.
<Anonymous>
Reply to: