[meta-freescale] Boot custom iMX6Q from eMMC 4.4.1

Mon Feb 1 09:25:04 PST 2016

Hi All,

I'm trying to setup a custom board, based on iMX6Q, to boot from eMMC 4.4.1.
The board boot correctly via USB OTG, current kernel config is kernel-fslc v4.1.

So far so good I've first tried to reach the boot_info under /sys/bus/mmc/devices/mmc1\:0001
in order to set the related eMMC boot info, but the give file is not present

/sys/devices/soc0/soc/2100000.aips-bus/219c000.usdhc/mmc_host/mmc1/mmc1:0001 # ls -al
drwxr-xr-x    4 root     root             0 Jan 27 16:43 .
drwxr-xr-x    4 root     root             0 Jan 27 16:43 ..
drwxr-xr-x    3 root     root             0 Jan 27 16:43 block
-r--r--r--    1 root     root          4096 Jan 27 16:52 cid
-r--r--r--    1 root     root          4096 Jan 27 16:52 csd
-r--r--r--    1 root     root          4096 Jan 27 16:52 date
lrwxrwxrwx    1 root     root             0 Jan 27 16:52 driver -> ../../../../../../../../bus/mmc/drivers/mmcblk
-r--r--r--    1 root     root          4096 Jan 27 16:52 enhanced_area_offset
-r--r--r--    1 root     root          4096 Jan 27 16:52 enhanced_area_size
-r--r--r--    1 root     root          4096 Jan 27 16:52 erase_size
-r--r--r--    1 root     root          4096 Jan 27 16:52 ffu_capable
-r--r--r--    1 root     root          4096 Jan 27 16:52 fwrev
-r--r--r--    1 root     root          4096 Jan 27 16:52 hwrev
-r--r--r--    1 root     root          4096 Jan 27 16:52 manfid
-r--r--r--    1 root     root          4096 Jan 27 16:43 name
-r--r--r--    1 root     root          4096 Jan 27 16:52 oemid
drwxr-xr-x    2 root     root             0 Jan 27 16:52 power
-r--r--r--    1 root     root          4096 Jan 27 16:52 preferred_erase_size
-r--r--r--    1 root     root          4096 Jan 27 16:52 prv
-r--r--r--    1 root     root          4096 Jan 27 16:52 raw_rpmb_size_mult
-r--r--r--    1 root     root          4096 Jan 27 16:52 rel_sectors
-r--r--r--    1 root     root          4096 Jan 27 16:43 serial
lrwxrwxrwx    1 root     root             0 Jan 27 16:43 subsystem -> ../../../../../../../../bus/mmc
-r--r--r--    1 root     root          4096 Jan 27 16:52 type
-rw-r--r--    1 root     root          4096 Jan 27 16:43 uevent

so far so good I've then tried to use the mmc commands below but the board refuses to boot likely
because the PARTION_CONFIG register set to 0x48.

/ # mmc bootpart enable 1 1 /dev/mmcblk0
/ # mmc extcsd read /dev/mmcblk0
=============================================
  Extended CSD rev 1.5 (MMC 4.41)
=============================================

Card Supported Command sets [S_CMD_SET: 0x01]
HPI Features [HPI_FEATURE: 0x03]: implementation based on CMD12
Background operations support [BKOPS_SUPPORT: 0x01]
Background operations status [BKOPS_STATUS: 0x02]
1st Initialisation Time after programmed sector [INI_TIMEOUT_AP: 0xf6]
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]
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: 0x06]
Secure Feature support [SEC_FEATURE_SUPPORT: 0x15]
Secure Erase Multiplier [SEC_ERASE_MULT: 0x02]
Secure TRIM Multiplier [SEC_TRIM_MULT: 0x03]
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: 0x06]
High-capacity erase unit size [HC_ERASE_GRP_SIZE: 0x08]
 i.e. 4096 KiB
High-capacity erase timeout [ERASE_TIMEOUT_MULT: 0x01]
Reliable write sector count [REL_WR_SEC_C: 0x01]
High-capacity W protect group size [HC_WP_GRP_SIZE: 0x02]
 i.e. 8192 KiB
Sleep current (VCC) [S_C_VCC: 0x08]
Sleep current (VCCQ) [S_C_VCCQ: 0x08]
Sleep/awake timeout [S_A_TIMEOUT: 0x10]
Sector Count [SEC_COUNT: 0x00ea0000]
 Device is block-addressed
Minimum Write Performance for 8bit:
 [MIN_PERF_W_8_52: 0x08]
 [MIN_PERF_R_8_52: 0x08]
 [MIN_PERF_W_8_26_4_52: 0x08]
 [MIN_PERF_R_8_26_4_52: 0x08]
Minimum Write Performance for 4bit:
 [MIN_PERF_W_4_26: 0x08]
 [MIN_PERF_R_4_26: 0x08]
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: 0x01]
Out-of-interrupt busy timing [OUT_OF_INTERRUPT_TIME: 0x02]
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: 0x48]**
** Boot Partition 1 enabled**
** No access to boot partition*
Boot config protection [BOOT_CONFIG_PROT: 0x00]
Boot bus Conditions [BOOT_BUS_CONDITIONS: 0x16]
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]: 0x01
Write reliability setting register [WR_REL_SET]: 0x00
 user area: existing data is at risk if a power failure occurs during a write operation
 partition 1: existing data is at risk if a power failure occurs during a write operation
 partition 2: existing data is at risk if a power failure occurs during a write operation
 partition 3: existing data is at risk if a power failure occurs during a write operation
 partition 4: existing data is at risk 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]: 0x03
 Device support partitioning feature
 Device can have enhanced tech.
Max Enhanced Area Size [MAX_ENH_SIZE_MULT]: 0x0001d4
 i.e. 3833856 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

Does anyone can suggest what to do?

Thanks in advance,
Roberto Fichera.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20160201/6485bfd1/attachment.html>