Skip to contentSkip to conversation

Ramdisk too big, CRC problem

U-Boot-Users Sonia Martinez 1 participant 1 message Oct 4, 2007

lore
Share & tools
lore
#0 lore raw

Hi to all,

I've been working without problems booting linux from RAM with uboot using this command:

bootm 340000 480000

My system has 32MB of RAM memory.

Linux image is bzip2 compressed occupying 1.2 MB. It's loaded in 0x00000000.

Ramdisk image is uncompressed, and with size up to 4MB there is no problem in booting the whole system, but if it grows to 5.6 MB a CRC problem appears.

Here is the log:

## Booting image at 00340000 ...
Header checksum 0x379FE185 calculated checksum 0x379FE185

   Image Name:   Linux-2.6.22.6
   Image Type:   PowerPC Linux Kernel Image (bzip2 compressed)
   Data Size:    1248712 Bytes =  1.2 MB

Load Address: 00000000
Entry Point: 00000000
Image checksum 0xC2C0A57C calculated 0xC2C0A57C
Verifying Checksum ... OK
Uncompressing Kernel Image ... Descompressed in 0x00000000 length 3121286
0x2FA086
OK
## Loading RAMDisk Image at 00480000 ...
Header checksum 0x936E410B calculated 0x936E410B

   Image Name:   Root
   Image Type:   PowerPC Linux RAMDisk Image (uncompressed)
   Data Size:    6156288 Bytes =  5.9 MB

Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... Bad Data CRC

It seems that the ramdisk image is corrupted because of the initialization of linux image. Can anyone help me? Is it something related to the descompression of bzip2 image?

Best regards,

Sonia

Signature · 2 lines
View this message in context: http://www.nabble.com/Ramdisk-too-big%2C-CRC-problem-tf4568069.html#a13037608
Sent from the Uboot - Users mailing list archive at Nabble.com.