08-27-2015 09:01 PM
I want to make my own ramdisk image based on the 2015.2-release.tar.xz (http://www.wiki.xilinx.com/Zynq+2015.2+Release) , but when I decompress the uramdisk.image.gz, it seems never to work,the file was not damaged:
root@ubuntu:/work/ramdisk/2015.2-release# ll total 19840 drwxr-xr-x 5 root root 4096 Aug 27 20:40 ./ drwxr-xr-x 6 root root 4096 Aug 27 20:42 ../ -rw-r--r-- 1 root root 10622952 Aug 27 20:22 2015.2-release.tar.xz drwxr-xr-x 2 root root 4096 Aug 27 20:24 tmp_mount/ -rw-r--r-- 1 11562 300 3478648 Jul 30 14:08 uImage -rw-r--r-- 1 11562 300 6186958 Jul 30 14:08 uramdisk.image.gz drwxr-xr-x 4 root root 4096 Aug 27 20:22 zc70x/ drwxr-xr-x 2 root root 4096 Aug 27 20:22 zed/ root@ubuntu:/work/ramdisk/2015.2-release# gunzip uramdisk.image.gz gzip: uramdisk.image.gz: not in gzip format root@ubuntu:/work/ramdisk/2015.2-release# tar -zxf uramdisk.image.gz gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now root@ubuntu:/work/ramdisk/2015.2-release# file uramdisk.image.gz uramdisk.image.gz: u-boot legacy uImage, , Linux/ARM, RAMDisk Image (gzip), 6186894 bytes, Thu Jul 30 14:08:02 2015, Load Address: 0x00000000, Entry Point: 0x00000000, Header CRC: 0x36C5DF9E, Data CRC: 0xDCD49C9
Is there any solution for me ?
08-28-2015 05:46 AM
08-27-2015 09:59 PM
check with ubuntu
08-27-2015 11:24 PM
Thanks for your repley!
But i am confused by the link you give me. It seems that I have a different problem with that.
I have the right directory, undamaged file, the root user .
Or ,is the file "uramdisk.image.gz" in the "2015.2-release.tar.xz" can not be decompressed ?
My same operation on the arm_ramdisk.image.gz(http://www.wiki.xilinx.com/Build+and+Modify+a+Rootfs) works normally. Is there any difference between the two files?
08-28-2015 04:37 AM
A long time ago we were using an initrd ramdisk but now it is an initramfs ramdisk. These are not tar based files but cpio based.
So there is a different process to alter the ramdisk image.
I hope that helps,
08-28-2015 05:46 AM
08-30-2015 08:13 PM
Thanks,the file can be decompressed when I remove the 64 byte header.
I can see the whole files in it's mounted directory :
But when I boot ZYNQ to the file system ,I can't see any of them .Seems like that it is empty:
I dont understand, someone get the reason?
08-30-2015 11:36 PM
Sorry, I was in the wrong directory. The default directory is in the home dirctory while the file systerm is mount on /root .