This is the partmap for Android 5.1 on the NanoPI3 boards. It works but the first entry seems to be too long and actually ends up 0x200 into the bootloader area. The start of 0x200 and length of 0x8e00 means that the end is 0x8200 and the bootloader starts at 0x8000. Older versions of this file are set for length of 0x7e00 for the 2ndboot.

The 2ndboot file is small (18K) so would not enter the bootloader space anyway, but it does seem rather strange)

Is this an error?

Code: Select all

# sd0 partition map
# flash= <device>.<dev no>:<partition>:<fstype>:<start>,<length>
#   support device : eeprom, nand, mmc
#   support fstype : 2nd, boot, raw, fat, ext4, ubi
#
flash=mmc,0:2ndboot:2nd:0x200,0x8e00;
flash=mmc,0:bootloader:boot:0x8000,0x77000;
flash=mmc,0:boot:fat:0x000100000,0x004000000:boot.img;
flash=mmc,0:system:ext4:0x04100000,0x2F200000:system.img;
flash=mmc,0:cache:ext4:0x33300000,0x1AC00000:cache.img;
flash=mmc,0:misc:emmc:0x4E000000,0x00800000;
flash=mmc,0:recovery:emmc:0x4E900000,0x01600000;
flash=mmc,0:userdata:ext4:0x50000000,0x0:userdata.img;