Actions
Forum Thread Details
  • State Not Answered
  • Replies 1 reply
  • Subscribers 299 subscribers
  • Views 443 views
  • Users 0 members are here
Related

zImage and uImage

ashahsana

Hello
I downloaded the release 14.7 version and I boot the 7z020 board by these files. In this version uImage, u-boot , uramdisk and fsbl is used.
After that I tried to make my own boot.bin file using sdk-> create boot image option, for this I used the the same files of fsbl and u-boot.
when I run this then it demands zImage and ramdisk32M.image.gz.
why?? I google it but I cannot find the answer.
Can anyone here explain me, why it happens?
thanks in advance

  • 0

    Sana,

    You will continue to run into outdated issues unless you upgrade to a new tool flow.  zimage was a format used for linux kernels in the past, and has been replaced by uimage.  Changes to the image format go in lock-step with uboot versions.  There is actually not much difference between the two, with a zimage being encapsulated in a wrapper with additional information on the image that is used by uboot.  The wrapper is created by a tool called mkimage, that is part of the Linux build environment.

    If you are trying to get Linux running, and you have little experience, I would highly recommend that you try downloading a PetaLinux BSP for the board you are targeting.  There are pre-built images in the design, and the environment will allow you to build from scratch and make small incremental changes that are easier to trace when things go wrong, rather than starting from a non-functioning image that could be due to any number of reasons.

    Always best to begin with something that works, and slowly move towards your goal, testing at each change.  

    Ron