• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 164 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

AM6411: unable to use the u-boot shell to create FAT partitions in the eMMC

AM625: How to boot by MMCSD (eMMC using UDA) boot mode

Jane Michael
Prodigy 20 points
Part Number: AM625

Tool/software:

Hi TI Teams:

       Our custom boards, based on AM6254ATGFHIAMCRQ1, are equiqed with eMMC by the interface of MMC 0 and do not have SD card.  We want to boot from eMMC and use USB DFU to fixed the uboot and Linux Image to eMMC. So we will fix the boot mode switch where the Primary Boot Mode is selected to USB DFU and the Backup Mode is selected to MMCSD BOOT finally, according to the documents "AM62x Processors Silicon Revision 1.0-Texas Instruments Families of Products-Technical Reference Manual" .  So we test our idea on AM62x-SK-EVM board right now because it can change the boot mode.

       According to the reference manual, the primary mode of usb dfu will switch to backup mode MMCSD after 1 min without any dfu operations. It works well according to our tests.

       But the question is that the MMCSD boot mode (eMMC iusing UDA) as backup mode need to be fat filesystem mode. So we firstly test that the EVM board boot from primary mode of MMCSD (eMMC using UDA) mode, including Fs or RAW mode, now it does not work well. Our question is how to boot by primary MMCSD (eMMC using UDA) mode and with Filesystem mode.  

       The following is out test record, we use ti sdk 10 (ti-processor-sdk-linux-rt-am62xx-evm-10.00.07.04-Linux-x86-Install).

       1. The boot mode switch B15 ~ B0 is set to be "0000 0000 1100 1010", and using dfu-util to excute dfu uboot

 

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
$ sudo dfu-util -l
sudo dfu-util -l
dfu-util 0.11
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
Found DFU: [0451:6165] ver=0200, devnum=109, cfg=1, intf=0, path="1-1", alt=1, name="SocId", serial="01.00.00.00"
Found DFU: [0451:6165] ver=0200, devnum=109, cfg=1, intf=0, path="1-1", alt=0, name="bootloader", serial="01.00.00.00"
$ sudo dfu-util -R -a bootloader -D tiboot3.bin
dfu-util 0.11
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
dfu-util: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
Opening DFU capable USB device...
Device ID 0451:6165
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

        2. After DFU uboot, the board can excute u-boot, then we set the eMMC partitions on host pc by terminal serial. The log is shown as following.

 

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
U-Boot SPL 2024.04-dirty (Dec 18 2024 - 08:25:16 +0800)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
SPL initial stack usage: 13392 bytes
Trying to boot from DFU
#######################################################DOWNLOAD ... OK
Ctrl+C to exit ...
Authentication passed
Authentication passed
Authentication passed
Loading Environment from nowhere... OK
init_env from device 10 not supported!
Authentication passed
Authentication passed
Starting ATF on ARM64 core...
NOTICE: BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE: BL31: Built : 16:09:05, Feb 9 2024
U-Boot SPL 2024.04-dirty (Dec 18 2024 - 08:25:40 +0800)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
SPL initial stack usage: 1904 bytes
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

        3. After setting eMMC partitions, we download the tiboot3.bin, tispl.bin, u-boot.img to eMMC through the dfu-utils.

  

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
$ sudo dfu-util -a boot -D tiboot3.bin
dfu-util 0.11
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
dfu-util: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
Opening DFU capable USB device...
Device ID 0451:6165
Device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 0110
Device returned transfer size 4096
Copying data from PC to DFU device
Download [=========================] 100% 292202 bytes
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

       The u-boot log of the board is shown ' download ok' and we set mmc settings of partconf and boot bus width as following shown.

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
##DOWNLOAD ... OK
Ctrl+C to exit ...
#####DOWNLOAD ... OK |
Ctrl+C to exit ...
####DOWNLOAD ... OK
Ctrl+C to exit ...
#######################################################################################################K
Ctrl+C to exit ...
=> mmc partconf 0 1 1 1
=> mmc partconf 0 1 7 1
=> mmc bootbus 0 2 0 0
Set to BOOT_BUS_WIDTH = 0x2, RESET = 0x0, BOOT_MODE = 0x0
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

       4. Then we reset the boot mode switch of B15 ~ B0 to MMCSD primary mode, "0000 0000 1100 0010"  or another try "0000 0000 1100 0011". The borad startup without any log outputing.

     We are in a hurry about this project, please reply as soon as possible.