[U-Boot-Users] Ramdisk: Bad Data CRC

Please help. I am trying to boot my system using a fairly large ramdisk (~24MB uncompressed, ~8MB compressed). I can tftp it up to my board fine, and can run imi, and it says the checksum is ok, but whenever I try to boot I get the following error:
=> tftp 400000 uRamdisk Speed: 100, full duplex Using MOTO ENET0 device TFTP from server 192.168.123.254; our IP address is 192.168.123.1 Filename 'uRamdisk'. Load address: 0x400000 Loading:
... I cut out all the # symbols ...
done Bytes transferred = 8527748 (821f84 hex) => imi 400000
## Checking Image at 00400000 ... Image Name: JJS Ramdisk Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size: 8527684 Bytes = 8.1 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK => bootm 200000 400000 ## Booting image at 00200000 ... Image Name: Linux-2.6.9 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 1234275 Bytes = 1.2 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Loading RAMDisk Image at 00400000 ... Image Name: JJS Ramdisk Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size: 8527684 Bytes = 8.1 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC
Is it too large of a ramdisk? If so, what is the maximum size allowed. I have 256MB of DDR SDRAM. This is a custom MPC8540 sytem.
Thanks, Jeff Stevens
__________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail

In message 20050208191113.12212.qmail@web41411.mail.yahoo.com you wrote:
=> bootm 200000 400000
...
Verifying Checksum ... Bad Data CRC
Is it too large of a ramdisk? If so, what is the maximum size allowed. I have 256MB of DDR SDRAM. This is a custom MPC8540 sytem.
Are you sure that smaller ramdisks are working on your system? It might be a problem with your system coniguration. Also, did you try loading the ramdisk to a higher address - like 0x1000000 ? Finally: did you read the README and try playing with different "initrd_high" settings?
Best regards,
Wolfgang Denk
participants (2)
-
Jeff Stevens
-
Wolfgang Denk