BPI-M2 Zero boot fail due to failure of android system mount

hi commiunity.

I tested the BPI-M2 Zero board with the android4.4 binary provided on this site and it worked very well. I created the BPI-M2 Zero image using the android7.0 source provided by Allwinner and tested it on the BPI-M2 Zero board. However, the following error occurred:

This is some log message at boot time.


[    5.098481] init: /dev/hw_random not found
[    5.105361] init: selected display policy: dual
[    5.110444] init: display.0: opened type(04) mode(04)
[    5.115189] init: write_file: Unable to open '/proc/sys/kernel/sched_tunable_scaling': No such file or directory
[    5.115255] init: write_file: Unable to open '/proc/sys/kernel/sched_latency_ns': No such file or directory
[    5.115315] init: write_file: Unable to open '/proc/sys/kernel/sched_wakeup_granularity_ns': No such file or directory
[    5.115373] init: write_file: Unable to open '/proc/sys/kernel/sched_compat_yield': No such file or directory
[    5.118112] init: write_file: Unable to write to '/dev/cpuctl/cpu.shares': Invalid argument
[    5.118191] init: write_file: Unable to open '/dev/cpuctl/cpu.rt_runtime_us': Permission denied
[    5.118254] init: write_file: Unable to open '/dev/cpuctl/cpu.rt_period_us': Permission denied
[    5.119055] init: write_file: Unable to open '/dev/cpuctl/bg_non_interactive/cpu.rt_runtime_us': Permission denied
[    5.119119] init: write_file: Unable to open '/dev/cpuctl/bg_non_interactive/cpu.rt_period_us': Permission denied
[    5.119589] audit: type=1400 audit(9.250:4): avc:  denied  { module_request } for  pid=1 comm="init" kmod="fs-cpuset" scontext=u:r:init:s0 tcontext=u:r:kernel:s0 tclass=system permissive=0
[    5.124127] init: write_file: Unable to open '/proc/sys/abi/swp': No such file or directory
[    5.145034] [NAND]Failed to insmod nand!!!
[    5.145636] init: /dev/hw_random not found
[    5.147521] FIVM init
[    5.147525] FIVM device register ok
[    5.256473] init: display.1: closed type(-1) mode(-1)
[    5.262087] init: do open device
[    5.265826] [DISP] disp_device_attached_and_enable,line:190:
[    5.271909] attached ok, mgr1<-->device0, type=2, mode=11
[    5.287370] init: Copy Layer: from channel 0 to channel 1
[    5.293407] init: Copy Layer: find layer channel 1 layer 0
[    5.299869] init: HDMI current output mode 4, supported
[    5.305715] init: close disp_device fd
[   25.037740] fs_mgr: soc is normal. (return value:0)
[   25.043254] fs_mgr: Don't verity system on normal chipset
**[   25.049467] fs_mgr: __mount(source=/dev/block/by-name/system,target=/system,type=ext4)=-1**
**[   25.058699] fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/by-name/system at /system options: (null) error: No such file or directory**
**[   45.043875] fs_mgr: check_fs(): mount(/dev/block/by-name/cache,/cache,ext4)=-1: No such file or directory**
**[   45.056906] setup_fs: executing /system/bin/setup_fs failed: No such file or directory**
**[   45.056906]**
**[   45.067431] setup_fs: setup_fs terminated by exit(255)**
[   45.067431]
[   45.075159] fs_mgr: Not running /system/bin/e2fsck on /dev/block/by-name/cache (executable not in system image)
[   45.086781] fs_mgr: __mount(source=/dev/block/by-name/cache,target=/cache,type=ext4)=-1
[   45.095774] fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/by-name/cache at /cache options: nomblk_io_submit,barrier=1,discard error: No such file or directory
[   65.044311] fs_mgr: check_fs(): mount(/dev/block/by-name/UDISK,/data,ext4)=-1: No such file or directory
[   65.057004] setup_fs: executing /system/bin/setup_fs failed: No such file or directory
[   65.057004]
[   65.067579] setup_fs: setup_fs terminated by exit(255)
[   65.067579]
[   65.075283] fs_mgr: Not running /system/bin/e2fsck on /dev/block/by-name/UDISK (executable not in system image)
[   65.086963] fs_mgr: __mount(source=/dev/block/by-name/UDISK,target=/data,type=ext4)=-1
[   65.095894] fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/by-name/UDISK at /data options: nomblk_io_submit,barrier=1,noauto_da_alloc,discard error: No such file or directory
[   85.035722] fs_mgr: start format /dev/block/by-name/Reserve0fs_mgr: wait for format /dev/block/by-name/Reserve0[   85.042561] fs_mgr: fork to format /dev/block/by-name/Reserve0 fileSystem: Fat16
fs_mgr: __mount(source=/dev/block/by-name/Reserve0,target=/Reserve0,type=vfat)=-1
[   85.064190] fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/by-name/Reserve0 at /Reserve0 options: (null) error: No such file or directory
[   85.080679] init: fs_mgr_mount_all returned an error
[   85.086266] init:
[   85.093038] init: ===============================================
[   85.099892] init: | This Android Device will start-up failed!!! |
[   85.106723] init: ===============================================
[   85.113495] init:
[   85.121049] init: fs_mgr_mount_all returned unexpected error 255

I understand that the BPI-M2 Zero does not support android 7.0 yet , so can not help it now. I would be very grateful if someone could help me with this.

Thank you.

Hmm, I think SDRAM is a problem. On other boards with 1G SDRAM, booting works well using same binary. BPI-M2 Zero has 512M SDRAM. so I think it is impossible on BPI-M2 Zero board.