Crash loading Ramdisk

Hi,

I have the following setup:

HW:
board: microzed + FMC carrier + FMCOMMS3
RTL: I took the reference design from here
http://wiki.analog.com/resources/fpga/docs/hdl
and ported it to microzed, remapping pins and removing unnecessary ports (i.e HDMI).

SW:
I got linux from
https://github.com/analogdevicesinc/linux
For the devicetree I used zynq-zed-adv7511-ad9361-fmcomms2-3.dts, also from ADI's linux distribution
The ramdisk is the one provided by Xilinx.

During boot I get

## Booting kernel from Legacy Image at 02080000 ...
   Image Name:   Linux-4.0.0-g86cfd8d
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3331976 Bytes = 3.2 MiB
   Load Address: 00008000
   Entry Point: 00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 04000000 ...
   Image Name:
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5309954 Bytes = 5.1 MiB
   Load Address: 00000000
   Entry Point: 00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
   Booting using the fdt blob at 0x2000000
   Loading Kernel Image ... OK
   Loading Ramdisk to 1faef000, end 1ffff602 ...

and the boot hangs.

Could you help with this issue?

Thanks,
Max

Parents

0 zedhed over 10 years ago

Hi suppamax,

If you look at zynq-zed-adv7511-ad9361-fmcomms2-3.dts which is governed by the hierarchy defined in zynq-zed.dtsi and if you look through that file you will see the following bootargs defined:

bootargs = "console=ttyPS0,115200 root=/dev/mmcblk0p2 rw earlyprintk rootfstype=ext4 rootwait";

That tells me that a RAM disk image is not even needed for what you are trying to do because the EXT4 partition on the SD card serves as the root file system, not a RAM disk.

My suggestion is to modify your U-boot just like jbattles did in this thread:

http://microzed.org/content/microzed-custom-u-boot-environment-variables-being-overwritten-boot

Using the U-boot command "bootm 0x3000000 - 0x2A00000" to bypass loading the RAMdisk into memory altogether.

Regards,

-Kevin
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 suppamax over 10 years ago in reply to zedhed

Hi Kevin,

thanks for your suggestion but I don't think the issue is related to u-boot nor ramdisk.

I made some experiments and I don't have this ramdisk loading issue if I use the current uImage and DTB but a different BOOT.bin (the current boot.bin uses the same uboot as the working one).
This suggests me that the problem is in hdl.

What do you think?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 suppamax over 10 years ago in reply to zedhed

Hi Kevin,

thanks for your suggestion but I don't think the issue is related to u-boot nor ramdisk.

I made some experiments and I don't have this ramdisk loading issue if I use the current uImage and DTB but a different BOOT.bin (the current boot.bin uses the same uboot as the working one).
This suggests me that the problem is in hdl.

What do you think?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data