AnsweredAssumed Answered

Building Linux for ZED board + FMCOMMS1

Question asked by jeffkt2 on May 12, 2015
Latest reply on May 18, 2015 by larsc

Hi,

 

I'm having a few issues trying to run linux by following the instructions here:

 

Linux with HDMI video output on the ZED and ZC702, ZC706 boards [Analog Devices Wiki]

 

Everything is just fine until I get to building the device tree. The zynq-zed-adv7511-xcomm.dts does not exist in my arch/armboot/dts folder. There does exist a zynq-zed-adv7511-fmcomms1.dts, so I used that to build the device tree:

 

make zynq-zed-adv7511-fmcomms1.dtb

 

The device tree blob was generated successfully, and I copied all files to the SD card. When I try to book the board, I get the following error messages over the uart:

 

U-Boot 2012.10-00430-g2678622 (Dec 11 2012 - 16:47:06)

DRAM:  512 MiB

WARNING: Caches not enabled

MMC:   SDHCI: 0

SF: Detected S25FL256S with page size 64 KiB, total 32 MiB

SF: Warning - Only lower 16MB is accessible in 3 byte addressing mode

*** Warning - bad CRC, using default environment

In:    serial

Out:   serial

Err:   serial

Net:   zynq_gem

Hit any key to stop autoboot:  0

Copying Linux from SD to RAM...

Device: SDHCI

Manufacturer ID: 3

OEM: 5344

Name: SU08G

Tran Speed: 50000000

Rd Block Len: 512

SD version 2.0

High Capacity: Yes

Capacity: 7.4 GiB

Bus Width: 4-bit

reading uImage

3267632 bytes read

reading devicetree.dtb

15666 bytes read

reading uramdisk.image.gz

** Unable to read "uramdisk.image.gz" from mmc 0:1 **

## Booting kernel from Legacy Image at 03000000 ...

   Image Name:   Linux-3.19.0-g5b0956e

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    3267568 Bytes = 3.1 MiB

   Load Address: 00008000

   Entry Point:  00008000

   Verifying Checksum ... OK

Wrong Ramdisk Image Format

Ramdisk image is corrupt or invalid

 

 

Any help would be greatly appreciated!

 

Thanks

Outcomes