Missing emmc boot0 and boot1

[lool]

Hi

qcom-ptool carries partitions.conf for qrb2210-rb1/emmc and unoq-16G/emmc, but only covering the "user" part of the emmc (the main physical partition). However, "boot0" and "boot1" are also relevant and used to convey CDT for both boards, and even MAC addresses for UNO Q.

qcom-ptool doesn't have yet support for boot0/boot1 emmc partitions, but once it does I think we should add the corresponding partitions.conf entries for these.

I'm creating this issue to track this and for @loicpoulain to share his notes on boot0/boot1 for RB1 and UNO Q.

[loicpoulain]

So on Rb1/Uno-Q, the CDT is part of BOOT1 (rawprogram2.xml):

<?xml version="1.0" ?>
<data>
  <!--NOTE: This is an ** Autogenerated file **-->
  <!--NOTE: Sector size is 512bytes-->
  <program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="cdt.bin" label="CDT" num_partition_sectors="4" partofsingleimage="false" physical_partition_number="2" readbackverify="false" size_in_KB="2.0" sparse="false" start_byte_hex="0x4400" start_sector="34"/>
  <program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="last_grow" num_partition_sectors="1" partofsingleimage="false" physical_partition_number="2" readbackverify="false" size_in_KB="0.5" sparse="false" start_byte_hex="0x4c00" start_sector="38"/>
  <program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="gpt_main2.bin" label="PrimaryGPT" num_partition_sectors="34" partofsingleimage="true" physical_partition_number="2" readbackverify="false" size_in_KB="17.0" sparse="false" start_byte_hex="0x0" start_sector="0"/>
  <program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="gpt_backup2.bin" label="BackupGPT" num_partition_sectors="33" partofsingleimage="true" physical_partition_number="2" readbackverify="false" size_in_KB="16.5" sparse="false" start_byte_hex="(512*NUM_DISK_SECTORS)-16896." start_sector="NUM_DISK_SECTORS-33."/>
</data>

On Uno-Q, BOOT0 is used to store WiFi Mac and Bluetooth BD addresses:

<?xml version="1.0" ?>
<data>
  <!--NOTE: This is an ** Autogenerated file **-->
  <!--NOTE: Sector size is 512bytes-->
  <program start_sector="34" size_in_KB="4.0" physical_partition_number="1" partofsingleimage="false" file_sector_offset="0" num_partition_sectors="8" readbackverify="false" filename="bdaddr.bin" sparse="false" start_byte_hex="0x4400" SECTOR_SIZE_IN_BYTES="512" label="bdaddr"/>
  <program start_sector="42" size_in_KB="4.0" physical_partition_number="1" partofsingleimage="false" file_sector_offset="0" num_partition_sectors="8" readbackverify="false" filename="wlanaddr.bin" sparse="false" start_byte_hex="0x5400" SECTOR_SIZE_IN_BYTES="512" label="wlanaddr"/>
  <program start_sector="50" size_in_KB="0" physical_partition_number="1" partofsingleimage="false" file_sector_offset="0" num_partition_sectors="0" readbackverify="false" filename="persist.bin" sparse="false" start_byte_hex="0x6400" SECTOR_SIZE_IN_BYTES="512" label="persist"/>
  <program start_sector="0" size_in_KB="17.0" physical_partition_number="1" partofsingleimage="true" file_sector_offset="0" num_partition_sectors="34" readbackverify="false" filename="gpt_main1.bin" sparse="false" start_byte_hex="0x0" SECTOR_SIZE_IN_BYTES="512" label="PrimaryGPT"/>
  <program start_sector="NUM_DISK_SECTORS-33." size_in_KB="16.5" physical_partition_number="1" partofsingleimage="true" file_sector_offset="0" num_partition_sectors="33" readbackverify="false" filename="gpt_backup1.bin" sparse="false" start_byte_hex="(512*NUM_DISK_SECTORS)-16896." SECTOR_SIZE_IN_BYTES="512" label="BackupGPT"/>
</data>

[lool]

persist.bin with size 0 is really weird; I thought persist was a HLOS partition used on some Yocto implementations

[lool]

Persist partition is discussed in #66

I'm convinced it should be handled as a HLOS partition and that a zero size makes no sense. I'd like to drop it entirely across all ptool platforms, but in the context of this issue, I think I want to add a standard-size persist like we have on other platforms.

[ndechesne]

size_in_KB = 0 is indeed weird. I am wondering what the actual GPT looks like..