cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
senkoo
Observer
Observer
4,106 Views
Registered: ‎08-28-2018

Ramdisk image is corrupt or invalid.

Jump to solution

Hello,

 

My name is Senna and I am working on the zc702 dev kit.

When i boot my kernel i get this and i have no clue on how i fix this... I looked through multiple posts but could'nt find my solution. 

 

Maybe it is something simple and can just tell me.

 

The boot log:

U-Boot 2017.01 (Oct 04 2018 - 08:48:19 +0000)

Board: Xilinx Zynq
DRAM:  ECC disabled 1 GiB
MMC:   sdhci_transfer_data: Error detected in status(0x208000)!
sdhci@e0101000: 0 (eMMC)
SF: Detected n25q1024 with page size 256 Bytes, erase size 4 KiB, total 128 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ZYNQ GEM: e000b000, phyaddr ffffffff, interface rgmii-id
PHY is not detected
GEM PHY init failed
No ethernet found.
U-BOOT for ets-prg

Hit any key to stop autoboot:  0
Zynq> sf probe
SF: Detected n25q1024 with page size 256 Bytes, erase size 4 KiB, total 128 MiB
Zynq> sf write 0x1000000 0x0 0x500000
device 0 offset 0x0, size 0x500000
SF: 5242880 bytes @ 0x0 Written: OK
Zynq> sf write 0x2000000 0x520000 0x50000
device 0 offset 0x520000, size 0x50000
SF: 327680 bytes @ 0x520000 Written: OK
Zynq> sf write 0x3000000 0x570000 0x1500000
device 0 offset 0x570000, size 0x1500000
SF: 22020096 bytes @ 0x570000 Written: OK
Zynq> boot
SF: Detected n25q1024 with page size 256 Bytes, erase size 4 KiB, total 128 MiB
device 0 offset 0x570000, size 0x1500000
SF: 22020096 bytes @ 0x570000 Read: OK
## Loading kernel from FIT Image at 01000000 ...
   Using 'conf@1' configuration
   Verifying Hash Integrity ... OK
   Trying 'kernel@0' kernel subimage
     Description:  Linux Kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x010000d4
     Data Size:    12169320 Bytes = 11.6 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x00008000
     Entry Point:  0x00008000
     Hash algo:    sha1
     Hash value:   2dbdf0a07467c5d9607fd9f50c61633096c23ae1
   Verifying Hash Integrity ... sha1+ OK
## Loading ramdisk from FIT Image at 01000000 ...
   Using 'conf@1' configuration
   Trying 'ramdisk@0' ramdisk subimage
     Description:  ramdisk
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0x01b9e89c
     Data Size:    8718256 Bytes = 8.3 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: unavailable
     Entry Point:  unavailable
     Hash algo:    sha1
     Hash value:   d2fa492bac0a16e91ef42d87be82008c05eb1667
   Verifying Hash Integrity ... sha1 error!
Bad hash value for 'hash@1' hash node in 'ramdisk@0' image node
Bad Data Hash
Ramdisk image is corrupt or invalid

 

 

 

0 Kudos
1 Solution

Accepted Solutions
trigger
Voyager
Voyager
4,085 Views
Registered: ‎09-14-2016

Ok so first you can start with an "hello or maybe Hi"...

 

We don't have any information about your setup:

- Build from scratch, yocto ? petalinux ?

- Do you have check its file ?

- 8.3 Mo for an uncompressed ramdisk ?

 

Have you try to check the Hash value and compare with sources ?

 

Cheers,

Trigger

View solution in original post

0 Kudos
5 Replies
johnvivm
Voyager
Voyager
4,086 Views
Registered: ‎08-16-2018

first think I would do is making sure the ramdisk image is ok

0 Kudos
trigger
Voyager
Voyager
4,086 Views
Registered: ‎09-14-2016

Ok so first you can start with an "hello or maybe Hi"...

 

We don't have any information about your setup:

- Build from scratch, yocto ? petalinux ?

- Do you have check its file ?

- 8.3 Mo for an uncompressed ramdisk ?

 

Have you try to check the Hash value and compare with sources ?

 

Cheers,

Trigger

View solution in original post

0 Kudos
senkoo
Observer
Observer
4,074 Views
Registered: ‎08-28-2018
For some reason i just re-ran petalinux-build and it was ok.. I really don't know what happened.
0 Kudos
senkoo
Observer
Observer
4,074 Views
Registered: ‎08-28-2018
my apologies,

I't doesnt seem to be a problem anymore. I dont know what went wrong or why...

Cheers,
Senko
0 Kudos
trigger
Voyager
Voyager
4,069 Views
Registered: ‎09-14-2016
cool :-)
0 Kudos