* [U-Boot-Users] Ramdisk too big, CRC problem
@ 2007-10-04 11:00 Sonia Martinez
0 siblings, 0 replies; 2+ messages in thread
From: Sonia Martinez @ 2007-10-04 11:00 UTC (permalink / raw)
To: u-boot
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
--
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [U-Boot-Users] Ramdisk too big, CRC problem
@ 2007-10-04 11:24 Sonia
0 siblings, 0 replies; 2+ messages in thread
From: Sonia @ 2007-10-04 11:24 UTC (permalink / raw)
To: u-boot
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 up to 5.6 MB a CRC problem appears.
Here is the log (I've added some prints):
## 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
____________________________________________________________________________________
S? un Mejor Amante del Cine
?Quieres saber c?mo? ?Deja que otras personas te ayuden!
http://advision.webevents.yahoo.com/reto/entretenimiento.html
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-10-04 11:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-10-04 11:00 [U-Boot-Users] Ramdisk too big, CRC problem Sonia Martinez
-- strict thread matches above, loose matches on Subject: below --
2007-10-04 11:24 Sonia
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox