[ARMedslack] A few questions on kirkwood initrd

Tyler T tylernt at gmail.com
Wed Jul 28 17:00:03 UTC 2010

>> Unfortunately, the Dockstar won't finish booting the resulting image
> It could be because the installer image is too large to fit in RAM, or
> into the addresses into which you're loading it.

I think you're right. We're getting into stuff I don't know much about, but:

# mkimage -l uImageInstaller
Image Name:   Slackware 13.1 Installer
Created:      Tue Jul 27 22:30:45 2010
Image Type:   ARM Linux Multi-File Image (uncompressed)
Data Size:    16795836 Bytes = 16402.18 kB = 16.02 MB
Load Address: 00008000
Entry Point:  00008000
   Image 0: 2096780 Bytes = 2047.64 kB = 2.00 MB
   Image 1: 14699044 Bytes = 14354.54 kB = 14.02 MB

I think I might see the issue. The Load Address / Entry Point appears
to be 32KB (00008000 is hex, I believe). This is probably fine for the
typical u-Boot environment, but I'm chainloading a second bootloader
so a Load Address of 32KB is probably right on top of my second
u-Boot. Will play with it this evening.

> By the way, I used the extracted initrd to install Armedslack on my
> SD/MMC based system and there was no problem (I extracted initrd to the
> MMC card and booted it as my system has to little RAM to use initrd
> directly).

That's clever. If I can't figure out the Load Address stuff, this
should be a good alternative.

More information about the ARMedslack mailing list