MPC Live X internal EMMC disk informations - TheKikGen/MPC-LiveXplore GitHub Wiki

This analysis was done with a serial USB TTL converter connected to the debug port of my MPC Live. Immediatly after powering on the MPC, it is necessary to strike any key to enter in the bootloader (Uboot).

Disk informations in UBoot

List of available emmc :

=> mmc list
dwmmc@ff0f0000: 0 (eMMC)

The internal onboard 16Go sdcard is not shown by the mmc list command, but it is scanned during the boot. However the external sdcard reader is not mounted.

The command mmc info give us miscellaneous internal emmc disk informations :

=> mmc info
Device: dwmmc@ff0f0000
Manufacturer ID: 45
OEM: 100
Name: SEM04
Tran Speed: 52000000
Rd Block Len: 512
MMC version 4.5
High Capacity: Yes
Capacity: 3.7 GiB
Bus Width: 8-bit
Erase Group Size: 256 KiB
HC WP Group Size: 8 MiB
User Capacity: 3.7 GiB WRREL
Boot Capacity: 2 MiB
RPMB Capacity: 2 MiB

The manufacturer is Hynix Semiconductor (Hyundai Electronics=45).

Disk partitioning :

=> mmc part

Partition Map for MMC device 0  --   Partition Type: EFI

Part    Start LBA       End LBA         Name
        Attributes
        Type GUID
        Partition GUID
  1     0x00000040      0x000000bf      "uboot-spl"
        attrs:  0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   3c7a21f6-7d1c-6949-8f05-88c0b9c0f0e6
  2     0x000000c0      0x000000cf      "env"
        attrs:  0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   8f868bbe-d889-f84f-a64d-d077e73b4f09
  3     0x00000100      0x000003ff      "uboot"
        attrs:  0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   92e71b46-293b-0a4c-a6a2-3460c0119cbe
  4     0x00000400      0x000023ff      "splash"
        attrs:  0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   cda9bf40-2c6d-224e-a662-f0a803794462
  5     0x00002400      0x000043ff      "recoverysplash"
        attrs:  0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   e2b850e0-92ee-ca43-98ad-9aa4fbca8616
  6     0x00004400      0x000fe3ff      "rootfs"
        attrs:  0x0000000000000004
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   24d1deac-3434-1a4e-98d1-68ee2945a5f1
  7     0x000fe400      0x0075ffde      "data"
        attrs:  0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   931ad49d-ad59-0849-833a-9bf00af5b60e

7 partitions :

  1. uboot-spl : the second-stage boot loader used to load UBoot in memory
  2. env : uboot environnement variables (text file)
  3. uboot : the main bootloader used to mount the system partition and launch the Linux kernel
  4. splash : splash screen (Linux frame buffer RGB format)
  5. recoverysplash : the red recovery "update mode" screen (Linux frame buffer BRGA format - 800x1280 32bits depth)
  6. rootfs : the linux ext4 file system, containing the MPC executable
  7. data : used to store MPC settings and internal expansions and demo/user projects. mmc hwpartition checks the HARDWARE emmc partioning. Do not play with other options of this very dangerous and unreversible command !
=> mmc hwpartition check
Partition configuration:
        No enhanced user data area
        No GP1 partition
        No GP2 partition
        No GP3 partition
        No GP4 partition

A special variable $partitions is set within Uboot, allowing to define how the GPT (disk partition table) is built. This variable can be then used to regenerate the GPT with the command "gpt write mmc 0 $partitions" directly in Uboot. This can save your MPC in case of a corrupted disk partition table (I had the case !). A "fastboot flash gpt gpt.img" should also work if you have a gpt backup img file but not tested...

partitions=uuid_disk=02bebde5-b5a4-48cd-b262-512fe8b6ae06;
name=uboot-spl,size=64KiB,start=32KiB,uuid=f6217a3c-1c7d-4969-8f05-88c0b9c0f0e6;
name=env,size=8KiB,start=96KiB,uuid=be8b868f-89d8-4ff8-a64d-d077e73b4f09;
name=uboot,size=384KiB,start=128KiB,uuid=461be792-3b29-4c0a-a6a2-3460c0119cbe;
name=splash,size=4MiB,uuid=40bfa9cd-6d2c-4e22-a662-f0a803794462;
name=recoverysplash,size=4MiB,uuid=e050b8e2-ee92-43ca-98ad-9aa4fbca8616;
name=rootfs,bootable,size=500MiB,uuid=acded124-3434-4e1a-98d1-68ee2945a5f1;
name=data,size=0,uuid=9dd41a93-59ad-4908-833a-9bf00af5b60e;

Disk informations in Linux :

/dev/mmcblk2: PTUUID="02bebde5-b5a4-48cd-b262-512fe8b6ae06" PTTYPE="gpt"
/dev/mmcblk2p1: PARTLABEL="uboot-spl" PARTUUID="3c7a21f6-7d1c-6949-8f05-88c0b9c0f0e6"
/dev/mmcblk2p2: PARTLABEL="env" PARTUUID="8f868bbe-d889-f84f-a64d-d077e73b4f09"
/dev/mmcblk2p3: PARTLABEL="uboot" PARTUUID="92e71b46-293b-0a4c-a6a2-3460c0119cbe"
/dev/mmcblk2p4: PARTLABEL="splash" PARTUUID="cda9bf40-2c6d-224e-a662-f0a803794462"
/dev/mmcblk2p5: PARTLABEL="recoverysplash" PARTUUID="e2b850e0-92ee-ca43-98ad-9aa4fbca8616"
/dev/mmcblk2p6: LABEL="root" UUID="a3bffe78-fd0c-4d1a-9e3d-f6101f733c0d" TYPE="ext4" PARTLABEL="rootfs" PARTUUID="24d1deac-3434-1a4e-98d1-68ee2945a5f1"
/dev/mmcblk2p7: LABEL="az01-internal" UUID="e683aba9-6c41-4270-bed7-7f239ab8ac68" TYPE="ext4" PARTLABEL="data" PARTUUID="931ad49d-ad59-0849-833a-9bf00af5b60e"
/dev/mmcblk0: PTTYPE="dos"
/dev/mmcblk0p1: UUID="6df1ed3a-f152-49ee-b7de-b3d9662ca920" TYPE="ext4"

Mount points vs partitions

  • Root file system / : type ext4 (ro,relatime)
  • Devices : devtmpfs on /dev type devtmpfs
  • Sys : sysfs on /sys type sysfs
  • proc on /proc type proc
  • tmpfs on /dev/shm type tmpfs rw
  • devpts on /dev/pts type devpts rw
  • /run : tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
  • tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  • cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
  • cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  • cgroup on /sys/fs/cgroup/debug type cgroup (rw,nosuid,nodev,noexec,relatime,debug)
  • cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  • cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
  • tmpfs on /etc/machine-id type tmpfs (ro,mode=755)
  • tmpfs on /media type tmpfs (rw)
  • debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
  • tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
  • fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
  • configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
  • Internal configuration (etc overlay) : /dev/mmcblk2p7 on /media/az01-internal type ext4 (rw,relatime)
  • overlay on /etc type overlay (rw,relatime,lowerdir=/etc,upperdir=/media/az01-internal/system/etc/overlay,workdir=/media/az01-internal/system/etc/.work)
  • overlay on /var type overlay (rw,relatime,lowerdir=/var,upperdir=/media/az01-internal/system/var/overlay,workdir=/media/az01-internal/system/var/.work)
  • Internal sd card : /dev/mmcblk0p1 on /media/az01-internal-sd type ext4 (rw,relatime)

More on partitions

The fdisk command shows all disks partitoning, including external sdcard, and or hard disk.

#fdisk -l

Device           Start     End Sectors  Size Type
/dev/mmcblk2p1      64     191     128   64K Microsoft basic data
/dev/mmcblk2p2     192     207      16    8K Microsoft basic data
/dev/mmcblk2p3     256    1023     768  384K Microsoft basic data
/dev/mmcblk2p4    1024    9215    8192    4M Microsoft basic data
/dev/mmcblk2p5    9216   17407    8192    4M Microsoft basic data
/dev/mmcblk2p6   17408 1041407 1024000  500M Microsoft basic data
/dev/mmcblk2p7 1041408 7733214 6691807  3.2G Microsoft basic data

Disk /dev/mmcblk2boot1: 2 MiB, 2097152 bytes, 4096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mmcblk2boot0: 2 MiB, 2097152 bytes, 4096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mmcblk0: 14.8 GiB, 15918432256 bytes, 31090688 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device         Boot Start      End  Sectors  Size Id Type
/dev/mmcblk0p1       8192 31090687 31082496 14.8G 83 Linux

Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Generic
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 4658432A-28F5-471D-9DEE-7AAB19522732

Device     Start       End   Sectors   Size Type
/dev/sda1   2048 976773134 976771087 465.8G Microsoft basic data
#

It is possible to dump the recovery spash screen directly to the framebuffer. The MPC application must be stopped before.


# systemctl stop inmusic-mpc
# cat /dev/mmcblk2p5 /dev/fb0
# systemctl start inmusic-mpc

gdisk command result for the internal emmc :

command (? for help): p
Disk /dev/mmcblk2: 7733248 sectors, 3.7 GiB
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 02BEBDE5-B5A4-48CD-B262-512FE8B6AE06
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 7733214
Partitions will be aligned on 64-sector boundaries
Total free space is 78 sectors (39.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1              64             191   64.0 KiB    0700  uboot-spl
   2             192             207   8.0 KiB     0700  env
   3             256            1023   384.0 KiB   0700  uboot
   4            1024            9215   4.0 MiB     0700  splash
   5            9216           17407   4.0 MiB     0700  recoverysplash
   6           17408         1041407   500.0 MiB   0700  rootfs
   7         1041408         7733214   3.2 GiB     0700  data

mmc "block" devices can be seen with a lsblock command, or a "ls /dev/mmc*" :

brw-rw----    1 root     disk      179, 128 Jan 23 18:28 /dev/mmcblk0
brw-rw----    1 root     disk      179, 129 Jan 23 18:28 /dev/mmcblk0p1
brw-rw----    1 root     disk      179,   0 Jan 23 18:28 /dev/mmcblk2
brw-rw----    1 root     disk      179,  32 Jan 23 18:28 /dev/mmcblk2boot0
brw-rw----    1 root     disk      179,  64 Jan 23 18:28 /dev/mmcblk2boot1
brw-rw----    1 root     disk      179,   1 Jan 23 18:28 /dev/mmcblk2p1
brw-rw----    1 root     disk      179,   2 Jan 23 18:28 /dev/mmcblk2p2
brw-rw----    1 root     disk      179,   3 Jan 23 18:28 /dev/mmcblk2p3
brw-rw----    1 root     disk      179,   4 Jan 23 18:28 /dev/mmcblk2p4
brw-rw----    1 root     disk      179,   5 Jan 23 18:28 /dev/mmcblk2p5
brw-rw----    1 root     disk      179,   6 Jan 23 18:28 /dev/mmcblk2p6
brw-rw----    1 root     disk      179,   7 Jan 23 18:28 /dev/mmcblk2p7
brw-rw----    1 root     disk      179,  96 Jan 23 18:28 /dev/mmcblk2rpmb

Linux presents the various emmc hardware partitions as separate devices:

  • /dev/mmcblk2boot0 - emmc hardware BOOT0 partition
  • /dev/mmcblk2boot1 - emmc hardware BOOT1 partition
  • /dev/mmcblk2rpmb - emmc RPMB partition
  • /dev/mmcblk2 - emmc USER partition

Emmc harware BOOT partitions are read-only by default as they are typically used for sensitive boot firmware. To write to them (DON'T DO THAT !) you can disable force_ro in sysfs via: echo 0 > /sys/class/block/mmcblk0boot0/force_ro

Know that hardware partionning is permanent and unreversible !

I have used the mmc-tool package to get more low level information about the emmc disk. MMC is a A VERY DANGEROUS TOOL : it can easily corrupt the GPT.

If your MPC is looping on the Update Mode, and you get error form the update software on the PC side, it is probably because the GPT is corrupted. Hopefully, the $partitions variable in UBoot env contains all partions info, and it is possible to regenerate the GPT in Uboot as written above.


# ./mmc extcsd read /dev/mmcblk2
=============================================
  Extended CSD rev 1.6 (MMC 4.5)
=============================================

Card Supported Command sets [S_CMD_SET: 0x01]
HPI Features [HPI_FEATURE: 0x01]: implementation based on CMD13
Background operations support [BKOPS_SUPPORT: 0x01]
Max Packet Read Cmd [MAX_PACKED_READS: 0x3f]
Max Packet Write Cmd [MAX_PACKED_WRITES: 0x3f]
Data TAG support [DATA_TAG_SUPPORT: 0x01]
Data TAG Unit Size [TAG_UNIT_SIZE: 0x03]
Tag Resources Size [TAG_RES_SIZE: 0x03]
Context Management Capabilities [CONTEXT_CAPABILITIES: 0x05]
Large Unit Size [LARGE_UNIT_SIZE_M1: 0x00]
Extended partition attribute support [EXT_SUPPORT: 0x00]
Generic CMD6 Timer [GENERIC_CMD6_TIME: 0x19]
Power off notification [POWER_OFF_LONG_TIME: 0x64]
Cache Size [CACHE_SIZE] is 0 KiB
Background operations status [BKOPS_STATUS: 0x00]
1st Initialisation Time after programmed sector [INI_TIMEOUT_AP: 0x0a]
Power class for 52MHz, DDR at 3.6V [PWR_CL_DDR_52_360: 0x00]
Power class for 52MHz, DDR at 1.95V [PWR_CL_DDR_52_195: 0x00]
Power class for 200MHz at 3.6V [PWR_CL_200_360: 0x00]
Power class for 200MHz, at 1.95V [PWR_CL_200_195: 0x00]
Minimum Performance for 8bit at 52MHz in DDR mode:
 [MIN_PERF_DDR_W_8_52: 0x00]
 [MIN_PERF_DDR_R_8_52: 0x00]
TRIM Multiplier [TRIM_MULT: 0x0e]
Secure Feature support [SEC_FEATURE_SUPPORT: 0x55]
Boot Information [BOOT_INFO: 0x07]
 Device supports alternative boot method
 Device supports dual data rate during boot
 Device supports high speed timing during boot
Boot partition size [BOOT_SIZE_MULTI: 0x10]
Access size [ACC_SIZE: 0x08]
High-capacity erase unit size [HC_ERASE_GRP_SIZE: 0x04]
 i.e. 2048 KiB
High-capacity erase timeout [ERASE_TIMEOUT_MULT: 0x0e]
Reliable write sector count [REL_WR_SEC_C: 0x01]
High-capacity W protect group size [HC_WP_GRP_SIZE: 0x04]
 i.e. 8192 KiB
Sleep current (VCC) [S_C_VCC: 0x08]
Sleep current (VCCQ) [S_C_VCCQ: 0x07]
Sleep/awake timeout [S_A_TIMEOUT: 0x13]
Sector Count [SEC_COUNT: 0x00760000]
 Device is block-addressed
Minimum Write Performance for 8bit:
 [MIN_PERF_W_8_52: 0x0a]
 [MIN_PERF_R_8_52: 0x0a]
 [MIN_PERF_W_8_26_4_52: 0x0a]
 [MIN_PERF_R_8_26_4_52: 0x0a]
Minimum Write Performance for 4bit:
 [MIN_PERF_W_4_26: 0x0a]
 [MIN_PERF_R_4_26: 0x0a]
Power classes registers:
 [PWR_CL_26_360: 0x00]
 [PWR_CL_52_360: 0x00]
 [PWR_CL_26_195: 0x00]
 [PWR_CL_52_195: 0x00]
Partition switching timing [PARTITION_SWITCH_TIME: 0x03]
Out-of-interrupt busy timing [OUT_OF_INTERRUPT_TIME: 0x19]
I/O Driver Strength [DRIVER_STRENGTH: 0x01]
Card Type [CARD_TYPE: 0x07]
 HS Dual Data Rate eMMC @52MHz 1.8V or 3VI/O
 HS eMMC @52MHz - at rated device voltage(s)
 HS eMMC @26MHz - at rated device voltage(s)
CSD structure version [CSD_STRUCTURE: 0x02]
Command set [CMD_SET: 0x00]
Command set revision [CMD_SET_REV: 0x00]
Power class [POWER_CLASS: 0x00]
High-speed interface timing [HS_TIMING: 0x01]
Erased memory content [ERASED_MEM_CONT: 0x00]
Boot configuration bytes [PARTITION_CONFIG: 0x00]
 Not boot enable
 No access to boot partition
Boot config protection [BOOT_CONFIG_PROT: 0x00]
Boot bus Conditions [BOOT_BUS_CONDITIONS: 0x00]
High-density erase group definition [ERASE_GROUP_DEF: 0x00]
Boot write protection status registers [BOOT_WP_STATUS]: 0x00
Boot Area Write protection [BOOT_WP]: 0x00
 Power ro locking: possible
 Permanent ro locking: possible
 ro lock status: not locked
User area write protection register [USER_WP]: 0x00
FW configuration [FW_CONFIG]: 0x00
RPMB Size [RPMB_SIZE_MULT]: 0x10
Write reliability setting register [WR_REL_SET]: 0x1f
 user area: the device protects existing data if a power failure occurs during a write operation
 partition 1: the device protects existing data if a power failure occurs during a write operation
 partition 2: the device protects existing data if a power failure occurs during a write operation
 partition 3: the device protects existing data if a power failure occurs during a write operation
 partition 4: the device protects existing data if a power failure occurs during a write operation
Write reliability parameter register [WR_REL_PARAM]: 0x05
 Device supports writing EXT_CSD_WR_REL_SET
 Device supports the enhanced def. of reliable write
Enable background operations handshake [BKOPS_EN]: 0x00
H/W reset function [RST_N_FUNCTION]: 0x00
HPI management [HPI_MGMT]: 0x01
Partitioning Support [PARTITIONING_SUPPORT]: 0x01
 Device support partitioning feature
 Device cannot have enhanced tech.
Max Enhanced Area Size [MAX_ENH_SIZE_MULT]: 0x0000ec
 i.e. 1933312 KiB
Partitions attribute [PARTITIONS_ATTRIBUTE]: 0x00
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00
 Device partition setting NOT complete
General Purpose Partition Size
 [GP_SIZE_MULT_4]: 0x000000
 [GP_SIZE_MULT_3]: 0x000000
 [GP_SIZE_MULT_2]: 0x000000
 [GP_SIZE_MULT_1]: 0x000000
Enhanced User Data Area Size [ENH_SIZE_MULT]: 0x000000
 i.e. 0 KiB
Enhanced User Data Start Address [ENH_START_ADDR]: 0x000000
 i.e. 0 bytes offset
Bad Block Management mode [SEC_BAD_BLK_MGMNT]: 0x00
Periodic Wake-up [PERIODIC_WAKEUP]: 0x00
Program CID/CSD in DDR mode support [PROGRAM_CID_CSD_DDR_SUPPORT]: 0x01
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[127]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[126]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[125]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[124]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[123]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[122]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[121]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[120]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[119]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[118]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[117]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[116]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[115]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[114]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[113]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[112]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[111]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[110]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[109]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[108]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[107]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[106]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[105]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[104]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[103]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[102]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[101]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[100]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[99]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[98]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[97]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[96]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[95]]: 0x02
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[94]]: 0x01
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[93]]: 0x04
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[92]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[91]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[90]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[89]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[88]]: 0x01
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[87]]: 0x01
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[86]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[85]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[84]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[83]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[82]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[81]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[80]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[79]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[78]]: 0x72
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[77]]: 0x35
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[76]]: 0x35
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[75]]: 0x69
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[74]]: 0x32
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[73]]: 0x32
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[72]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[71]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[70]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[69]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[68]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[67]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[66]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[65]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[64]]: 0x00
Native sector size [NATIVE_SECTOR_SIZE]: 0x00
Sector size emulation [USE_NATIVE_SECTOR]: 0x00
Sector size [DATA_SECTOR_SIZE]: 0x00
1st initialization after disabling sector size emulation [INI_TIMEOUT_EMU]: 0x00
Class 6 commands control [CLASS_6_CTRL]: 0x00
Number of addressed group to be Released[DYNCAP_NEEDED]: 0x00
Exception events control [EXCEPTION_EVENTS_CTRL]: 0x0000
Exception events status[EXCEPTION_EVENTS_STATUS]: 0x0000
Extended Partitions Attribute [EXT_PARTITIONS_ATTRIBUTE]: 0x0000
Context configuration [CONTEXT_CONF[51]]: 0x00
Context configuration [CONTEXT_CONF[50]]: 0x00
Context configuration [CONTEXT_CONF[49]]: 0x00
Context configuration [CONTEXT_CONF[48]]: 0x00
Context configuration [CONTEXT_CONF[47]]: 0x00
Context configuration [CONTEXT_CONF[46]]: 0x00
Context configuration [CONTEXT_CONF[45]]: 0x00
Context configuration [CONTEXT_CONF[44]]: 0x00
Context configuration [CONTEXT_CONF[43]]: 0x00
Context configuration [CONTEXT_CONF[42]]: 0x00
Context configuration [CONTEXT_CONF[41]]: 0x00
Context configuration [CONTEXT_CONF[40]]: 0x00
Context configuration [CONTEXT_CONF[39]]: 0x00
Context configuration [CONTEXT_CONF[38]]: 0x00
Context configuration [CONTEXT_CONF[37]]: 0x00
Packed command status [PACKED_COMMAND_STATUS]: 0x00
Packed command failure index [PACKED_FAILURE_INDEX]: 0x00
Power Off Notification [POWER_OFF_NOTIFICATION]: 0x01
Control to turn the Cache ON/OFF [CACHE_CTRL]: 0x00