Hi,
is there a actual description of the actual purpose
of all the partitions on the eMMC?
Is https://github.com/96boards/documentation/wiki/HiKeyGettingStarted#appendix-1-partition-information sufficient or do you need more details?
fastboot1 - l-loader.bin (stage 1 bootloader)
ptable - ptable-.img (partition map info)
mcuimage - mcuimage.bin (system control and power firmware)
fastboot - fip.bin (arm trusted firmware/bootloaders, including uefi/u-boot images)
nvme - nvme.img (storage of uefi non-volatile variables)
boot - boot-fat.uefi.img (fastboot app, grub app and grub config file)
cache - cache.img
system - system.img
userdata - userdata-.img
For the Debian build the system and userdata partitions are merged to create a single system (root file system) partition.
For Android partitions (cache, system, userdata), see http://www.addictivetips.com/mobile/android-partitions-explained-boot-system-recovery-data-cache-misc/. userdata is also called the ‘data’ partition.
thanks,
I think the extra details you gave should be added
to the table.
@vchong Great information. But the l-loader currently unable to create the userdata partition.
Number Start (sector) End (sector) Size Code Name
1 256 511 1024.0 KiB 0700 vrl
2 512 3583 12.0 MiB 0700 fastboot
3 3584 5119 6.0 MiB 0700 nvme
4 5120 8191 12.0 MiB 8300 fip
5 8192 73727 256.0 MiB 0700 cache
6 73728 73983 1024.0 KiB 0700 fw_lpm3
7 73984 90367 64.0 MiB EF00 boot
8 90368 94463 16.0 MiB 0700 dts
9 94464 94975 2.0 MiB 0700 trustfirmware
10 94976 1295103 4.6 GiB 8300 system
11 1295104 1495807 784.0 MiB 0700 vendor
12 1495808 1496063 1024.0 KiB 0700 reserved
Do you have any idea how to fix this problem?
l-loader : testing/hikey960_v1.2
arm-trusted-firmware : integration
OpenPlatfomrPkg : testing/hikey960_v1.3.4
uefi-tools : master (pulled on August 31 2017)
edk2 : testing/hikey960_v2.5
These are the git branches I am using to build ATF for Android on Hikey960 board.
You’re probably using the ptable for linux. Try the one for android, i.e. ptable-aosp-32g.img.
