Ramdisk image corrupt error while fusing

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Ramdisk image corrupt error while fusing

1,540件の閲覧回数
suchitasharma
Contributor I

We are using T1040 based board and trying to fuse linux,ramdisk and dtb images on the board. If we are  tftping all the Images and boot from RAM then Images are booted successfully . But when  we are tried fusing Images on NOR flash and booted using  command "bootm e8020000 e9300000 e8800000", we are facing error:

## Loading init Ramdisk from Legacy Image at e9300000 ...
Image Name: rootfs.ext2.gz.uboot
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 33254400 Bytes = 31.7 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid

 

Kindly help us the resolve this issue.

0 件の賞賛
返信
3 返答(返信)

1,517件の閲覧回数
suchitasharma
Contributor I

 

Hi,

    please see the log below,it looks fine

=> mw.b 1000000 0xa5 10000
=> protect off all
Un-Protect Flash Bank # 1
Un-Protect Flash Bank # 2
=> erase e9300000 e931ffff

. done
Erased 1 sectors
=> cp.b 1000000 e9300000 10000
Copy to Flash... 9....8....7....6....5....4....3....2....1....done
=> cmp.b 1000000 e9300000 10000
Total of 65536 byte(s) were the same
=> md e9300000
e9300000: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................
e9300010: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................
e9300020: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................
e9300030: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................
e9300040: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................
e9300050: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................
e9300060: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................
e9300070: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................
e9300080: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................
e9300090: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................
e93000a0: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................
e93000b0: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................
e93000c0: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................
e93000d0: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................
e93000e0: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................
e93000f0: a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 ................

0 件の賞賛
返信

1,497件の閲覧回数
yipingwang
NXP TechSupport
NXP TechSupport

Please verify the following commands.

=> tftp 0x10000000 nxa22585/t1040rdb/fsl-image-core-t1040d4rdb.ext2.gz.u-boot
=> protect off all
=> erase e9300000 +$filesize

=> cp.b 10000000 e9300000 $filesize
=> cmp.b 10000000 e9300000 $filesize
=>

0 件の賞賛
返信

1,521件の閲覧回数
yipingwang
NXP TechSupport
NXP TechSupport

Probably there is IFC timing configuration problem in u-boot, which causes problems to read/write NOR flash.

Please try the following test in u-boot on your target board.

=> mw.b 1000000 0xa5 10000

=> protect off all

=> erase e9300000 e931ffff
=> cp.b 1000000 e9300000 10000
=> cmp.b 1000000 e9300000 10000

For IFC timing configuration, you could refer to this document https://community.nxp.com/t5/Layerscape-Knowledge-Base/IFC-Controller-Configuration-on-QorIQ-Custom-...

 

 

 

0 件の賞賛
返信