How to successfully get the partition table with nvflash C:\nvflash3lt>nvflash ‐‐getpartitiontable partitiontable.txt ‐‐blob blob_new.bin ‐‐bl bootloader_encrypt_new.bin ‐‐go Nvflash v1.8.90246 started Using blob v1.1.57813;.MSC rcm version 0X20001 System Information: chip name: t20 chip id: 0x20 major: 1 minor: 4 chip sku: 0x8 chip uid: 0x043c8040421ff117 macrovision: disabled hdcp: enabled sbk burned: true dk burned: true boot device: emmc operating mode: 4 device config strap: 0 device config fuse: 0 sdram config strap: 0 downloading bootloader ‐‐ load address: 0x108000 entry point: 0x108000 sending file: bootloader_encrypt_new.bin \ 1393296/1393296 bytes sent bootloader_encrypt_new.bin sent successfully waiting for bootloader to initialize bootloader downloaded successfully Succesfully updated partition table information to partitiontable.txt Partition table for a 64Gb lt P9516 (3G model) PartitionId=2 Name=BCT DeviceId=18 StartSector=0 NumSectors=1024 BytesPerSector=4096 PartitionId=3 Name=PT DeviceId=18 StartSector=1024 NumSectors=512 BytesPerSector=4096 PartitionId=4 Name=EBT DeviceId=18 StartSector=1536 NumSectors=1024 BytesPerSector=4096 PartitionId=5 Name=GP1 DeviceId=18 StartSector=2560 NumSectors=512 BytesPerSector=4096 Page 1 PartitionId=6 Name=SOS DeviceId=18 StartSector=3072 NumSectors=1536 BytesPerSector=4096 PartitionId=7 Name=LNX DeviceId=18 StartSector=4608 NumSectors=2048 BytesPerSector=4096 PartitionId=8 Name=APP DeviceId=18 StartSector=6656 NumSectors=107520 BytesPerSector=4096 PartitionId=9 Name=CAC DeviceId=18 StartSector=114176 NumSectors=32768 BytesPerSector=4096 PartitionId=10 Name=MSC DeviceId=18 StartSector=146944 NumSectors=512 BytesPerSector=4096 PartitionId=11 Name=USP DeviceId=18 StartSector=147456 NumSectors=35840 BytesPerSector=4096 PartitionId=12 Name=UDA DeviceId=18 StartSector=183296 NumSectors=14447616 BytesPerSector=4096 PartitionId=13 Name=TMP DeviceId=18 StartSector=14630912 NumSectors=614400 BytesPerSector=4096 PartitionId=14 Name=GPT DeviceId=18 StartSector=15245312 NumSectors=276480 BytesPerSector=4096 Page 2 How to successfully get the bootloader BCT with nvflash C:\nvflash3lt>nvflash ‐‐bct bct‐lt.bct ‐‐getbct ‐‐blob blob_new.bin ‐‐bl bootloader_encrypt_new.bin ‐‐go Nvflash v1.8.90246 started Using blob v1.1.57813;.MSC rcm version 0X20001 System Information: chip name: t20 chip id: 0x20 major: 1 minor: 4 chip sku: 0x8 chip uid: 0x043c8040421ff117 macrovision: disabled hdcp: enabled sbk burned: true dk burned: true boot device: emmc operating mode: 4 device config strap: 0 device config fuse: 0 sdram config strap: 0 retrieving bct into: bct‐lt.bct bct‐lt.bct received successfully downloading bootloader ‐‐ load address: 0x108000 entry point: 0x108000 sending file: bootloader_encrypt_new.bin \ 1393296/1393296 bytes sent bootloader_encrypt_new.bin sent successfully waiting for bootloader to initialize bootloader downloaded successfully There are only a few bits different between K1.bct and LT.bct Page 3 How to successfully read the BCT partition 2 with nvflash C:\nvflash3lt>nvflash ‐‐read 2 bootloader‐lt‐p9516.bin ‐‐blob blob_new.bin ‐‐bl bootloader_encrypt_new.bin ‐‐go Nvflash v1.8.90246 started Using blob v1.1.57813;.MSC rcm version 0X20001 System Information: chip name: t20 chip id: 0x20 major: 1 minor: 4 chip sku: 0x8 chip uid: 0x043c8040421ff117 macrovision: disabled hdcp: enabled sbk burned: true dk burned: true boot device: emmc operating mode: 4 device config strap: 0 device config fuse: 0 sdram config strap: 0 downloading bootloader ‐‐ load address: 0x108000 entry point: 0x108000 sending file: bootloader_encrypt_new.bin \ 1393296/1393296 bytes sent bootloader_encrypt_new.bin sent successfully waiting for bootloader to initialize bootloader downloaded successfully receiving file: bootloader‐lt‐p9516.bin, expected size: 4194304 bytes / 4194304/0 bytes received file received successfully (need to remove padding zeroes) Page 4 How to successfully read the EBT (bootloader.bin partition 4 with nvflash C:\nvflash3lt>nvflash ‐‐read 4 bootloader‐lt‐p9516.bin ‐‐blob blob_new.bin ‐‐bl bootloader_encrypt_new.bin ‐‐go Nvflash v1.8.90246 started Using blob v1.1.57813;.MSC ^C C:\nvflash3lt>nvflash ‐‐read 4 bootloader‐lt‐p9516.bin ‐‐blob blob_new.bin ‐‐bl bootloader_encrypt_new.bin ‐‐go Nvflash v1.8.90246 started Using blob v1.1.57813;.MSC rcm version 0X20001 System Information: chip name: t20 chip id: 0x20 major: 1 minor: 4 chip sku: 0x8 chip uid: 0x043c8040421ff117 macrovision: disabled hdcp: enabled sbk burned: true dk burned: true boot device: emmc operating mode: 4 device config strap: 0 device config fuse: 0 sdram config strap: 0 downloading bootloader ‐‐ load address: 0x108000 entry point: 0x108000 sending file: bootloader_encrypt_new.bin \ 1393296/1393296 bytes sent bootloader_encrypt_new.bin sent successfully waiting for bootloader to initialize bootloader downloaded successfully receiving file: bootloader‐lt‐p9516.bin, expected size: 4194288 bytes / 4194288/0 bytes received file received successfully (need to remove padding zeroes) Page 5 TEST 3 (UNSUCCESSFUL – PARTITION ERROR) nvflash.exe ‐‐blob blob_new.bin ‐‐bct flash_encrypt_new.bct ‐‐setbct ‐‐odmdata 0x30098011 ‐‐configfile flash.cfg ‐‐
configfile flash.cfg ‐‐bl bootloader_encrypt_new.bin ‐‐sync c:\nvflash3>nvflash.exe ‐‐blob blob_new.bin ‐‐bct flash_encrypt_new.bct –setbct ‐‐odmdata 0x30098011 ‐‐configfile flash.cfg ‐‐configfile flash.cfg ‐‐bl bootloader_encrypt_new.bin ‐‐sync Nvflash v1.8.90246 started Using blob v1.1.57813MSC rcm version 0X20001 System Information: chip name: t20 chip id: 0x20 major: 1 minor: 4 chip sku: 0x8 chip uid: 0x043c8040421ff117 macrovision: disabled hdcp: enabled sbk burned: true dk burned: true boot device: emmc operating mode: 4 device config strap: 0 device config fuse: 0 sdram config strap: 0 sending file: flash_encrypt_new.bct ‐ 4080/4080 bytes sent flash_encrypt_new.bct sent successfully odm data: 0x30098011 downloading bootloader ‐‐ load address: 0x108000 entry point: 0x108000 sending file: bootloader_encrypt_new.bin \ 1393296/1393296 bytes sent bootloader_encrypt_new.bin sent successfully waiting for bootloader to initialize bootloader downloaded successfully failed executing command 26 NvError 0x120002 command failure: sync failed (bad data) bootloader status: partition table is invalid, missing required information (code: 14) message: nverror:0x4 (0x4) flags: 0 As a result : This is written on the tablet screen Entering NvFlash recovery mode / Nv3p Server Page 6 

xPC Target supported Ethernet chipsets

Form 61-1498

AR6MXQ-DEV Datasheet

Datasheet - Advantech