DRA72XEVM: eMMC MLO boot issue on dra72ex-evm board

RAJ.M

Part Number: DRA72XEVM

Hi All,

we are using DRA72x_Jacinto_6 evm. We try to boot eMMC boot. we followed below link

e2e.ti.com/.../544018

1. set sw5 boot switch as select ENABLE MMC2 MUX (low)

2. set sysboot SW2[5..0] = 100010 [sd ,emmc]

3. using this script to write to emmc #./mk-eMMC-boot.sh --device /dev/mmcblk0

4. EXT_CSD register set using mmc utilities #mmc bootpart enable 1 1 /dev/mmcblk0boot0

5. for verifying read back

root@dra7xx-evm:~# mmc extcsd read /dev/mmcblk0boot0
=============================================
Extended CSD rev 1.6 (MMC 4.5)
=============================================

Card Supported Command sets [S_CMD_SET: 0x01]
HPI Features [HPI_FEATURE: 0x03]: implementation based on CMD12
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: 0x00]
Data TAG Unit Size [TAG_UNIT_SIZE: 0x00]
Tag Resources Size [TAG_RES_SIZE: 0x00]
Context Management Capabilities [CONTEXT_CAPABILITIES: 0x00]
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: 0xff]
Cache Size [CACHE_SIZE] is 0 KiB
Background operations status [BKOPS_STATUS: 0x01]
1st Initialisation Time after programmed sector [INI_TIMEOUT_AP: 0x32]
Power class for 52MHz, DDR at 3.6V [PWR_CL_DDR_52_360: 0x04]
Power class for 52MHz, DDR at 1.95V [PWR_CL_DDR_52_195: 0x09]
Power class for 200MHz at 3.6V [PWR_CL_200_360: 0x09]
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: 0x03]
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: 0x40]
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: 0x06]
Sleep current (VCCQ) [S_C_VCCQ: 0x09]
Sleep/awake timeout [S_A_TIMEOUT: 0x10]
Sector Count [SEC_COUNT: 0x00e80000]
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: 0x02]
[PWR_CL_52_360: 0x02]
[PWR_CL_26_195: 0x05]
[PWR_CL_52_195: 0x05]
Partition switching timing [PARTITION_SWITCH_TIME: 0x01]
Out-of-interrupt busy timing [OUT_OF_INTERRUPT_TIME: 0x04]
I/O Driver Strength [DRIVER_STRENGTH: 0x0f]
Card Type [CARD_TYPE: 0x17]
HS200 Single Data Rate eMMC @200MHz 1.8VI/O
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: 0x02]
Erased memory content [ERASED_MEM_CONT: 0x00]
Boot configuration bytes [PARTITION_CONFIG: 0x49]
Boot Partition 1 enabled
R/W Boot Partition 1
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]: 0x01
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]: 0x03
Device support partitioning feature
Device can have enhanced tech.
Max Enhanced Area Size [MAX_ENH_SIZE_MULT]: 0x0001d0
i.e. 3801088 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]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[94]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[93]]: 0x00
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]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[87]]: 0x00
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]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[77]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[76]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[75]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[74]]: 0x00
Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[73]]: 0x00
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

6.After flashing eMMC using ./mk-eMMC-boot.sh script. then we removed sdcard and try to boot from eMMC, but its not booting.

We have found eMMC boot is working in following case(Only when we have boot switch selects for both SD boot and eMMC boot).

1. Boot from SD card run "reset" command from u-boot. Then it will start boot from eMMC.

2. Boot from SD card stop it in u-boot. then remove the SD card and press switch (sw9 or sw4) it will start boot from

=> reset
resetting ...

U-Boot SPL 2016.05 (Apr 27 2017 - 15:41:43)
DRA722-GP ES2.0
Trying to boot from MMC2_2
reading u-boot.img
reading u-boot.img
reading u-boot.img
reading u-boot.img

U-Boot 2016.05-00001-g89866d1-dirty (Feb 24 2017 - 16:09:59 +0530)

CPU : DRA722-GP ES2.0
Model: TI DRA722 Rev C EVM
Board: DRA72x EVM REV C.1
DRAM: 2 GiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
part_get_info_efi: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
part_get_info_efi: *** ERROR: Invalid Backup GPT ***
ERROR: cannot find partition: 'userdata'

at arch/arm/cpu/armv7/omap-common/utils.c:195/mmc_get_part_size()
Warning: fastboot.userdata_size: unable to calc
SCSI: SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst
scanning bus for devices...
Found 0 device(s).
Net:   Could not get PHY for ethernet@48484000: addr 2
eth0: ethernet@48484000
Hit any key to stop autoboot: 0

Regards,

RAJ M

over 6 years ago

0 Mariya Petkova over 6 years ago

TI__Expert 4885 points

Hi, RAJ.M,

Your query has been forwarded to eMMC expert.

Regards,
Mariya

0 Mariya Petkova over 6 years ago in reply to Mariya Petkova

TI__Expert 4885 points

Hi, RAJ.M,

The expert's answer is:
It seems that you are using mk-emmc-boot script which flashes the boot/rootfs to eMMC userdata partition. But you are configuring eMMC to boot from boot partition - 4. EXT_CSD register set using mmc utilities #mmc bootpart enable 1 1 /dev/mmcblk0boot0

What do you want to boot from eMMC or use alternative boot (from bootpart)?

Regards,
Mariya

0 Mariya Petkova over 6 years ago in reply to Mariya Petkova

TI__Expert 4885 points

In addition, if you want to to use alternative boot then suggest them to refer to Technical Reference Manual "32.3.7.6.2.4 eMMC Partitions Handling in Alternative Boot Operation Mode"

If you want to just boot using eMMC then they don’t need to set the bootpartition just use the script and set sysboot to eMMC
Update bootargs accordingly.

Regards,
Mariya

0 Mariya Petkova over 6 years ago in reply to Mariya Petkova

TI__Expert 4885 points

RAJ.M,

The same issue is commented here with some more details:

Regards,

Mariya

0 RAJ.M over 6 years ago in reply to Mariya Petkova

Expert 2440 points

Hi Mariya,

What do you want to boot from eMMC or use alternative boot (from bootpart)?

I just want to boot from emmc.

It seems that you are using mk-emmc-boot script which flashes the boot/rootfs to eMMC userdata partition. But you are configuring eMMC to boot from boot partition - 4. EXT_CSD register set using mmc utilities #mmc bootpart enable 1 1 /dev/mmcblk0boot0

Now i configured user area. below my mmc exdcsd register read value.

Boot configuration bytes [PARTITION_CONFIG: 0x79]
User Area Enabled for boot
R/W Boot Partition 1

H/W reset function [RST_N_FUNCTION]: 0x01

1. set sw5 boot switch as {7..0} [00010000]

2. set sysboot SW2[5..0] = 100010 [first boot - sd ,second boot - emmc]

Still i cant boot MLO from eMMC

Regards,

RAJ M

0 RAJ.M over 6 years ago in reply to RAJ.M

Expert 2440 points

Hi All,

Any updates...

Regards,
RAJ M

0 Pavel Botev over 6 years ago in reply to RAJ.M

TI__Guru**** 170625 points

Raj,

You need to set also DIP Switch SW5.3 = ON in J6Eco (DRA72x) TI EVM for eMMC memory boot, see below document:

www.ti.com/.../spruib9.pdf

See also below wiki pages:

processors.wiki.ti.com/.../Processor_SDK_Linux_Automotive_Software_Developers_Guide
processors.wiki.ti.com/.../Linux_Core_U-Boot_User's_Guide

Regards,
Pavel

0 RAJ.M over 6 years ago in reply to Pavel Botev

Expert 2440 points

Hi Pavel,

Its not working even after changing DIP switch SW5.3=ON

But we observed that when we press SW4(power reset) its start booting from eMMC.

why it needs a power reset to work?

Regards,
RAJ M

0 Pavel Botev over 6 years ago in reply to RAJ.M

TI__Guru**** 170625 points

Raj,

You configure SW2/SW3 sysboot[15:0] for SD boot, and never switch to eMMC boot.

After you flash the eMMC (from SD card), power of the board, remove SD card, change SW2/SW3 sysboot pins for eMMC mode, and power on the board.

SW2[7:0] is sysboot[7:0], should be 00111000 for eMMC boot.

SW3[8:1] is sysboot[15:8], try with sysboot14 = 0, sysboot15 = 0

Regards,
Pavel

0 RAJ.M over 6 years ago in reply to Pavel Botev

Expert 2440 points

Hi Pavel,

Its working now.

But we want to boot below scenario

If SD card present it should boot from SD card, if SD not present it should boot from eMMC.

Booting Devices Order
SD eMMC

What is the sysboot[0-15] configuration?

Regards,
RAJ M

0 Pavel Botev over 6 years ago in reply to RAJ.M

TI__Guru**** 170625 points

Raj,

sysboot[5:0] = 100010 for 1st SD, 2nd eMMC

sysboot[5:0] = 111000 for eMMC only

See DRA72x TRM, Table 33-9. Booting Devices Order

Regards,
Pavel

0 RAJ.M over 6 years ago in reply to Pavel Botev

Expert 2440 points

Hi Pavel,

 sysboot[5:0] = 100010 for 1st SD, 2nd eMMC

In this setting

We have found eMMC boot is working in following case(Only when we have boot switch selects for both SD boot and eMMC boot).

1. Boot from SD card run "reset" command from u-boot. Then it will start boot from eMMC.

2. Boot from SD card stop it in u-boot. then remove the SD card and press switch (sw9 or sw4) it will start boot from eMMC

Regards,

RAJ M

0 Pavel Botev over 6 years ago in reply to RAJ.M

TI__Guru**** 170625 points

Raj,

Do you still have some questions? If no, please mark that thread as verified.

Regards,
Pavel

0 RAJ.M over 6 years ago in reply to Pavel Botev

Expert 2440 points

Hi Pavel,

Sorry I posted previous thread wrongly.

Still we faced eMMC booting issue,

In sysboot[5:0] = 100010 for 1st SD, 2nd eMMC setting

After power up when we press SW4(power reset) then only it start booting from eMMC. [SD card not present]

Regards,
RAJ M

0 Pavel Botev over 6 years ago in reply to RAJ.M

TI__Guru**** 170625 points

RAJ.M said:
Still we faced eMMC booting issue,

RAJ.M said:
After power up when we press SW4(power reset) then only it start booting from eMMC. [SD card not present]

What is the eMMC booting issue exactly? I am not able to understand your request. What exactly you need to know regarding eMMC boot?

Regards,
Pavel

0 RAJ.M over 6 years ago in reply to Pavel Botev

Expert 2440 points

Hi Pavel,

In sysboot[5:0] = 100010 for 1st SD, 2nd eMMC setting

If SD card inserted its booting directly from SD card, its fine.
If SD card not inserted it should boot from eMMC but its not booting. when we press SW4(power reset) then only it start booting from eMMC.

why eMMC is booting after pressing SW4(power reset)?

Regards,
RAJ M

0 Ravikumar Kattekola over 6 years ago in reply to RAJ.M

TI__Expert 4230 points

Hi Raj,

Try setting SW5-3 to high, on a few EVMs the dip switch (SW5) was mounted wrong.

1. set sw5 boot switch as select ENABLE MMC2 MUX (low)

Also if you are using aPG2.0 silicon (Rev H EVM) set SW3 -15 = 1

Regards,

0 RAJ.M over 6 years ago in reply to Ravikumar Kattekola

Expert 2440 points

Hi RK,

Try setting SW5-3 to high,

I have set already.

Also if you are using aPG2.0 silicon (Rev H EVM) set SW3 -15 = 1

I have set SW3 -15 = 1 already. I am not sure about our board silicon rev.

Regards,

RAJ M

0 Pavel Botev over 6 years ago in reply to RAJ.M

TI__Guru**** 170625 points

Raj,

RAJ.M said:
If SD card not inserted it should boot from eMMC but its not booting. when we press SW4(power reset) then only it start booting from eMMC.

why eMMC is booting after pressing SW4(power reset)?

How exactly you are trying to boot from eMMC in this case (sysboot[5:0] = 100010 1st SD, 2nd eMMC, no SD card inserted)? Please provide me the exact steps.

Note that sysboot pins are latched (valid) only after POR (Power On Reset). On DRA72x TI EVM, SW4 push button initiate POR for a complete SoC reset. SW5 is for warm reset.

See DRA72x DM, Table 4-29. Sysboot Signal Descriptions - The value latched on this pin upon porz reset release will determine the boot mode configuration of the device.

The same info we have also in DRA72x TRM, Table 3-24. External Boot Signals - Latched at power-on reset (POR)

sysboot[15:0] pins are captured at POR in CTRL_CORE_BOOTSTRAP[15:0] bit field. You can examine this register values in your various configurations.

Regards,
Pavel

0 Pavel Botev over 6 years ago in reply to Pavel Botev

TI__Guru**** 170625 points

Raj,

Make sure also you don't just unplug/plug the power cable to boot from eMMC in sysboot[5:0] = 100010 case. See the below e2e thread for more info:

e2e.ti.com/.../2160774

Regards,
Pavel

0 RAJ.M over 6 years ago in reply to Pavel Botev

Expert 2440 points

Hi Pavel,

How exactly you are trying to boot from eMMC in this case (sysboot[5:0] = 100010 1st SD, 2nd eMMC, no SD card inserted)? Please provide me the exact steps.

In sysboot[5:0] = 111000 for eMMC only

When we just unplug/plug the power cable to boot. its working fine.

In sysboot[5:0] = 100010 for 1st SD, 2nd eMMC

1. Insert the SD card when we just unplug/plug the power cable to boot. its proberly booting from SD.

2. Remove the SD card when we just unplug/plug the power cable to boot. after pressing the SW4(power reset) then only it start booting from eMMC.

Regards,

RAJ M

0 Stanislav Stilyanov over 6 years ago in reply to RAJ.M

TI__Genius 15120 points

Hi RAJ,

Please let me know if my understanding is correct:

In sysboot[5:0] = 100010 for 1st SD, 2nd eMMC;

- you are powering up the board w/o SD card -----> Board is not booting

- Then you are pressing POR reset switch -----> Board is booting fine from eMMC

0 Stanislav Stilyanov over 6 years ago in reply to Stanislav Stilyanov

TI__Genius 15120 points

Can you please dump the contents of:
0x4A00 26C4
0x4AE0 C204

0 RAJ.M over 6 years ago in reply to Stanislav Stilyanov

Expert 2440 points

Hi Stanislav Stilyanov,

yes exactly the case.

Regards,
RAJ M

0 RAJ.M over 6 years ago in reply to Stanislav Stilyanov

Expert 2440 points

hi Stanislav Stilyanov,

Below i read from uBoot.

=> md 0x4AE0C204
1b9bc02f

=> md 0x4A0026C4
00008122

we dnot have jtag to read before booting.

Regards,
Raj M

0 Stanislav Stilyanov over 6 years ago in reply to RAJ.M

TI__Genius 15120 points

Thanks Raj,

=> md 0x4AE0C204
1b9bc02f

You have silicon revision 2.0.

=> md 0x4A0026C4
00008122

You have sysboot[15] = 1 (I know you already mentioned that previously.)

DRA72x family is different than DRA75x/DRA74x, and has funny misalignment with regard to sysboot[15].

In fact, you should change it to 0 to allow eMMC boot. You can see this in the latest DRA72x TRM.

I really hope this helps because I don't know other reasons for the issue.

Regards,

Stan

0 Ravikumar Kattekola over 6 years ago in reply to Stanislav Stilyanov

TI__Expert 4230 points

Stan,

Thanks for pointing out that sysboot[15] should be 0 for dra72x unlike dra75x.

Regards,

0 Stanislav Stilyanov over 6 years ago in reply to Ravikumar Kattekola

TI__Genius 15120 points

You're welcome!
We did that update when we were releasing J6eco SR2.0 TRM for the first time. That's why it was on top of my head.

Regards,
Stan

Processors

Processors forum

DRA72XEVM: eMMC MLO boot issue on dra72ex-evm board