AnsweredAssumed Answered

imx6sl cannot fidisk ramdisk.img correctly

Question asked by Joshua Zhu on Oct 24, 2016
Latest reply on Oct 25, 2016 by gusarambula

Dear All,

 

Thanks for your help about the question!

 

ALSA device list:
  #0: imx-spdif
RAMDISK: gzip image found at block 0
UDF-fs: warning (device ram0): udf_fill_super: No partition found (2)
F2FS-fs (ram0): Magic Mismatch, valid(0xf2f52010) - read(0x65643030)
F2FS-fs (ram0): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (ram0): Magic Mismatch, valid(0xf2f52010) - read(0x642f0a30)
F2FS-fs (ram0): Can't find valid F2FS filesystem in 2th superblock
F2FS-fs (ram0): Magic Mismatch, valid(0xf2f52010) - read(0x65643030)
F2FS-fs (ram0): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (ram0): Magic Mismatch, valid(0xf2f52010) - read(0x642f0a30)
F2FS-fs (ram0): Can't find valid F2FS filesystem in 2th superblock
UDF-fs: warning (device ram0): udf_fill_super: No partition found (2)
F2FS-fs (ram0): Magic Mismatch, valid(0xf2f52010) - read(0x65643030)
F2FS-fs (ram0): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (ram0): Magic Mismatch, valid(0xf2f52010) - read(0x642f0a30)
F2FS-fs (ram0): Can't find valid F2FS filesystem in 2th superblock
F2FS-fs (ram0): Magic Mismatch, valid(0xf2f52010) - read(0x65643030)
F2FS-fs (ram0): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (ram0): Magic Mismatch, valid(0xf2f52010) - read(0x642f0a30)
F2FS-fs (ram0): Can't find valid F2FS filesystem in 2th superblock
List of all partitions:
0100            8192 ram0  (driver?)
0101            8192 ram1  (driver?)
0102            8192 ram2  (driver?)
0103            8192 ram3  (driver?)
0104            8192 ram4  (driver?)
0105            8192 ram5  (driver?)
0106            8192 ram6  (driver?)
0107            8192 ram7  (driver?)
0108            8192 ram8  (driver?)
0109            8192 ram9  (driver?)
010a            8192 ram10  (driver?)
010b            8192 ram11  (driver?)
010c            8192 ram12  (driver?)
010d            8192 ram13  (driver?)
010e            8192 ram14  (driver?)
010f            8192 ram15  (driver?)
No filesystem could mount root, tried:  ext3 ext2 ext4 vfat msdos iso9660 ntfs fuseblk udf f2fs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

 

I  do it:

 

android-info.txt              imx6sl-evk-csi.dtb        recovery.img
boot.img                      installed-files.txt       recovery-imx6sl.img
boot-imx6sl.img               kernel                    root
clean_steps.mk                obj                       symbols
dex_bootjars                  previous_build_config.mk  system
fake_packages                 ramdisk.img               system.img
fsl-sdcard-partition-f2fs.sh  ramdisk-recovery.img      system_raw.img
fsl-sdcard-partition.sh       recovery                  u-boot.imx
gen                           recovery.id               u-boot-imx6sl.imx

 

dd:  boot-imx6sl.img  recovery-imx6sl.img  system_raw.img u-boot-imx6sl.imx 
Would you like for help me?
With Best Regards
Joshua

Outcomes