This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Rebuilt Ramdisk does not boot

Other Parts Discussed in Thread: OMAP3530

Using OMAP3530, PSP  I would like to build a ramdisk image and load it over tftp.  Unfortunately, the boot process is hanging after "RAMDISK: gzip image found at block 0".

The process I am using to build the ramdisk image:
  mkdir -p ramdisk
dd if=/dev/zero of=ramdisk_file bs=40M count=1
mkfs.ext2 ramdisk_file
sudo mount -o loop ramdisk_file ramdisk
sudo tar -xvzf arago-console-image-omap3evm.tar.gz -C ramdisk
sudo umount ramdisk
gzip ramdisk_file

My boot arguments:

setenv get_kernel      run nand_kernel
setenv get_initrd      run tftp_initrd
setenv nand_kernel     nand read.i 0x80000000 280000 300000
setenv tftp_initrd     tftpboot 0x81600000 ramdisk_file.gz
setenv rdargs 'setenv bootargs mem=99M console=ttyS0,115200n8 root=/dev/ram0 rw initrd=0x81600000,40M ramdisk_size=40960'
setenv boot_rd 'run get_kernel; run get_initrd; run rdargs; bootm 0x80000000'

I load the ramdisk over tftp fine, the kernel boots up as normal, it gets to the ramdisk section, spits out "RAMDISK: gzip image found at block 0" and then hangs.  I have tried this with a prebuilt ramdisk image from DVSDK 3.00 and it boots fine.  What might I be doing wrong in my process?

Thank you,

Glenn Wainwright