Actions
Forum Thread Details
  • State Not Answered
  • Replies 3 replies
  • Subscribers 354 subscribers
  • Views 464 views
  • Users 0 members are here
Related

Hangup at Uncompressing Linux... done, booting the kernel.

Former Member

I am facing some problems in this project. We have made a zynq board but It doesn't have all the peripherals of zed board (external ports etc). My aim is to prepare the three file i.e BOOT.bin, devicetree.dtb and zImage (already have this) and put these into sd card and get the linux working.

Steps I am following to make the device tree are :
1. generating a xilinx.dts using the xilinx sdk.
2. converting the generated xilinx.dts to devicetree.dtb using the device tree compiler.
source: (http://www.wiki.xilinx.com/Build+Device+Tree+Blob)

Is this the correct method to do it Or I need to manually edit the generated xilinx.dts to add some parts and then convert it to .dtb format?


Steps I am following to generate the BOOT.bin.
xilinxtools-> create zynq boot image -> u-boot.bin -> rename it to BOOT.bin.


I have a zImage for the board.

Now I put these three files in the boot partition and plugin the sd card in slot.
I get the following issues:

case 1:
If I use my old BOOT.bin and old devicetree.dtb and zImage. ( by old I mean that in Old design I did not add the filter_vdma and filter_engine block).
I get everything fine the root@mcontroller prompt and on the monitor I see the linux icon.
These files were prepared by some one else.

case 2:
If I use my new BOOT.bin and old devicetree.dtb and zImage.
linux gets installed but the hdmi port does not work, It does not display the linux icons on the monitor but I get the root@mcontroller prompt.


case 3:
If I use my new BOOT.bin and new devicetree.dtb (both generated by above mentioned methods) and zImage.
In this case During the automatic boot, linux hangs up at this point: 
Uncompressing Linux... done, booting the kernel.


u200BI am not sure whether the steps I am following are correct or there is some mistake.
Or where exactly is the mistake.

Parents
  • 0

    Hi newbie,

    In case 3, are you using a new zImage as well?

    If it is the same zImage, one low impact thing you can try is to look through devicetree.dts to see if there are any obvious hardware differences that would hang the system up (like peripherals mapped to different address spaces).  You might look first to the places where you know the hardware mapping could have changed.

    If that does not work, you can eliminate most devices from the devicetree and see if you can get a minimal system booting.  Once the system is booting, you can add device entries back in one at a time to try and narrow down the culprit device.

    Regards,

    -Kevin

Reply
  • 0

    Hi newbie,

    In case 3, are you using a new zImage as well?

    If it is the same zImage, one low impact thing you can try is to look through devicetree.dts to see if there are any obvious hardware differences that would hang the system up (like peripherals mapped to different address spaces).  You might look first to the places where you know the hardware mapping could have changed.

    If that does not work, you can eliminate most devices from the devicetree and see if you can get a minimal system booting.  Once the system is booting, you can add device entries back in one at a time to try and narrow down the culprit device.

    Regards,

    -Kevin

Children