• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 100 subscribers
  • Views 514 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.

SK-AM62: Unable to Flash eMMC over USB DFU

Dimitri M.
Prodigy 11 points
Part Number: SK-AM62

Hi

I'm currently trying to flash the external eMMC chip of the eval board. I've roughly followed the posted how to guild. 

Environment:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
Hardware: AM62x SKEVM PROC114E3
Software: Custom
U-Boot (2023.04):
Repo: https://git.ti.com/git/ti-u-boot/ti-u-boot.git
Tag: 09.00.00.004
ti-k3-image-gen:
Repo: https://git.ti.com/cgit/k3-image-gen/k3-image-gen
Tag: 09.00.00.001
op-tee:
Repo: https://github.com/OP-TEE/optee_os/
Tag: 3.19.0
arm-trusted-firmware-version:
Repo: https://github.com/ARM-software/arm-trusted-firmware
Tag: v2.7.0
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

I've configured the board to boot into the USB Peripheral Mode. And it is also visible through the dfu-utils tool.

I've also build the tiboot3.bin, tispl.bin and u-boot.img according to the documentation in the ti-u-boot repo. And now I'm encountering some issues.

# First Issue

The usb dfu boot procedure seems to be a bit broken. 

Host Steps:

Fullscreen
1
2
3
4
5
6
# Step 1
sudo dfu-util -R -a bootloader -D ~/workdir/build-out/images/tiboot3-usbdfu.bin --device ,0451:*
# Step 2
sudo dfu-util -a tispl.bin -D ~/workdir/build-out/images/tispl.bin --device ,0451:*
# Step 3
sudo dfu-util -R -a u-boot.img -D ~/workdir/build-out/images/u-boot.img --device ,0451:*
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Target Log:

# Step 1 Result:

Fullscreen
1
2
3
4
U-Boot SPL 2023.04 (Jun 27 2023 - 13:12:20 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.1--v09.00.01 (Kool Koala)')
SPL initial stack usage: 13392 bytes
Trying to boot from DFU
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

# Step 2 & 3 Result:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Trying to boot from DFU
################################################DOWNLOAD ... OK
Ctrl+C to exit ...
###############################################DOWNLOAD ... OK
Ctrl+C to exit ...
alloc space exhausted
Could not get FIT buffer of 979524 bytes
check CONFIG_SYS_SPL_MALLOC_SIZE
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Loading Environment from nowhere... OK
init_env from device 10 not supported!
Starting ATF on ARM64 core...
NOTICE: BL31: v2.7(release):
NOTICE: BL31: Built : 13:12:43, Jun 27 2023
I/TC:
I/TC: OP-TEE version: Unknown_3.19 (gcc version 10.3.1 20210621 (GNU Toolchain for the A-profile Architecture 10.3-2021.07 (arm-10.29))) #1 Tue Jun 27 13:12:53 UTC 2023 aarch64
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

As you can see the tispl.bin and u-boot.img files where successfully uploaded but then the u-boot spl seems to be stuck and not starting the u-boot.img. It also presents the error: `Error (-2): cannot determine file size`. But I press Ctrl+C it will anyway start the u-boot.img. So I'm not entirely sure what here the problem is.

# Second Issue

Now I'm trying to upload the u-boot.img, tiboot3.bin, tispl.bin and rootfs files.

U-Boot Steps:

Fullscreen
1
2
3
4
# Step 1
env set dfu_alt_info $dfu_alt_info_emmc
# Step 2
dfu 0 mmc 0
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Host Steps:

Fullscreen
1
2
3
4
5
6
7
8
# Step 1
sudo dfu-util -a tiboot3.bin.raw -D ~/workdir/build-out/images/tiboot3.bin --device ,0451:*
# Step 2
sudo dfu-util -a tispl.bin.raw -D ~/workdir/build-out/images/tispl.bin --device ,0451:*
# Step 3
sudo dfu-util -a u-boot.img.raw -D ~/workdir/build-out/images/u-boot.img --device ,0451:*
# Step 4
sudo dfu-util -R -a rootfs -D ~/workdir/build-out/images/rootfs.ext2 --device ,0451:*
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

This all seem to work fine except the Host Step 4 which would upload the rootfs. This is not working. Here the u-boot quits uploading the image and presents the error: `Request would exceed designated area!`

Fun Fact: If I'm performing the same steps and set in Target Step 1 dfu_alt_info_mmc it works totally fine to upload all the data to an external SD-Card. So I'm not sure why I cannot upload the data to the internal emmc.

Some additional information:

U-Boot Env:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
addr_fit=0x90000000
arch=arm
args_all=setenv optargs ${optargs} earlycon=ns16550a,mmio32,0x02800000 ${mtdparts}
args_mmc=run finduuid;setenv bootargs console=${console} ${optargs} root=PARTUUID=${uuid} rw rootfstype=${mmcrootfstype}
args_ospi_nand=setenv bootargs console=${console} ${optargs} ubi.mtd=${ospi_nand_bootpart} root=${ospi_nand_bootvolume} rootfstype=ubifs
baudrate=115200
board=am62x
board_name=am62x_skevm
board_rev=E3
board_serial=0228
board_software_revision=01
boot=mmc
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
boot_efi_binary=load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootaa64.efi; if fdt addr -q ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r};else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi
boot_efi_bootmgr=if fdt addr -q ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr;fi
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_syslinux_conf}
boot_fdt=try
boot_fit=0
boot_net_usb_start=usb start
boot_prefixes=/ /boot/
boot_rprocs=if test ${dorprocboot} -eq 1 && test ${boot} = mmc; then rproc init; run boot_rprocs_mmc; fi;
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Full log files:

Host Log:

host-emmc.log
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
sudo dfu-util -R -a bootloader -D ~/workdir/build-out/images/tiboot3-usbdfu.bin --device ,0451:* || exit 0
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/
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 512
Copying data from PC to DFU device
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Target Log:

targt-emmc.log
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
U-Boot SPL 2023.04 (Jun 27 2023 - 13:12:20 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.1--v09.00.01 (Kool Koala)')
SPL initial stack usage: 13392 bytes
Trying to boot from DFU
################################################DOWNLOAD ... OK
Ctrl+C to exit ...
###############################################DOWNLOAD ... OK
Ctrl+C to exit ...
alloc space exhausted
Could not get FIT buffer of 979524 bytes
check CONFIG_SYS_SPL_MALLOC_SIZE
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Loading Environment from nowhere... OK
init_env from device 10 not supported!
Starting ATF on ARM64 core...
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

U-Boot generated .config files:

Make with am62x_r5_usbdfu_defconfig:

config-am62x-r5-defconfig.txt
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
#
# Automatically generated file; DO NOT EDIT.
# U-Boot 2023.04 Configuration
#
#
# Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
#
CONFIG_CREATE_ARCH_SYMLINK=y
CONFIG_SYS_CACHE_SHIFT_6=y
CONFIG_SYS_CACHELINE_SIZE=64
CONFIG_LINKER_LIST_ALIGN=4
# CONFIG_ARC is not set
CONFIG_ARM=y
# CONFIG_M68K is not set
# CONFIG_MICROBLAZE is not set
# CONFIG_MIPS is not set
# CONFIG_NIOS2 is not set
# CONFIG_PPC is not set
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Make with am62x_evm_a52_defconfig

config-am62x-evm-a52-defconfig.txt
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
#
# Automatically generated file; DO NOT EDIT.
# U-Boot 2023.04 Configuration
#
#
# Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
#
CONFIG_CREATE_ARCH_SYMLINK=y
CONFIG_SYS_CACHE_SHIFT_6=y
CONFIG_SYS_CACHELINE_SIZE=64
CONFIG_LINKER_LIST_ALIGN=8
# CONFIG_ARC is not set
CONFIG_ARM=y
# CONFIG_M68K is not set
# CONFIG_MICROBLAZE is not set
# CONFIG_MIPS is not set
# CONFIG_NIOS2 is not set
# CONFIG_PPC is not set
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0
    Prodigy 11 points

    I've already tried ti-u-boot-2021-01, and the outcome is similar. The first Issue is still present. U-Boot still gets stuck and only continues when pressing Ctrl+C. The only difference is that the error message is gone.

    I'm also already using the mentioned kernel version.

    U-Boot Log:

    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 2021.01 (Jun 29 2023 - 07:08:23 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.1--v09.00.01 (Kool Koala)')
    SPL initial stack usage: 13424 bytes
    Trying to boot from DFU
    ###############################################DOWNLOAD ... OK
    Ctrl+C to exit ...
    ############################################DOWNLOAD ... OK
    Ctrl+C to exit ...
    Loading Environment from MMC... MMC Device 0 not found
    *** Warning - No MMC card found, using default environment
    init_env from device 10 not supported!
    Starting ATF on ARM64 core...
    NOTICE: BL31: v2.7(release):
    NOTICE: BL31: Built : 07:08:40, Jun 29 2023
    I/TC:
    I/TC: OP-TEE version: Unknown_3.19 (gcc version 10.3.1 20210621 (GNU Toolchain for the A-profile Architecture 10.3-2021.07 (arm-10.29))) #1 Thu Jun 29 07:08:50 UTC 2023 aarch64
    I/TC: WARNING: This OP-TEE configuration might be insecure!
    I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
    I/TC: Primary CPU initializing
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Dimitri M.
    TI__Expert 8410 points

    Hi Dimitri,

    Recently discovered there might be an issue with USB DFU flashing to eMMC. Please give me a day or so and I will try on my end.

    ~ Judith

  • 0 in reply to Judith Mendez
    TI__Expert 8410 points

    Hi Dimitri,

    First issue: I went through the process again on u-boot 2021.01 and was not able to replicate your error. Can you please show me the log where you try with u-boot 2021.01?

    ~ Judith

  • 0
    Prodigy 11 points

    Hi Judith,

    I've already done this. See my reply related to the U-Boot 2021.01

  • 0
    Prodigy 11 points

    Maybe another comment. After some more testing I've realized that the provided tutorial is not complete. What do I mean by that:

    According to the U-Boot environment:

    Fullscreen
    1
    dfu_alt_info_emmc=rawemmc raw 0 0x800000 mmcpart 1;rootfs part 0 1 mmcpart 0;tiboot3.bin.raw raw 0x0 0x400 mmcpart 1;tispl.bin.raw raw 0x400 0x1000 mmcpart 1;u-boot.img.raw raw 0x1400 0x2000 mmcpart 1;u-env.raw raw 0x3400 0x100 mmcpart 1;sysfw.itb.raw raw 0x3600 0x800 mmcpart 1
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Here the important part is:

    Fullscreen
    1
    rootfs part 0 1 mmcpart 0
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Which indicates that there must be a partition to which the rootfs is written to. But mine has none. So could you give me the exact steps you did to have a fully working setup? 

    I'm also a bit confused. According to https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/08_06_00_42/exports/docs/linux/Foundational_Components/U-Boot/UG-Memory.html. There are several partitions:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    boot0 partition (8 MB) user partition
    0x0+----------------------------------+ 0x0+-------------------------+
    | tiboot3.bin (1 MB) | | |
    0x400+----------------------------------+ | |
    | tispl.bin (2 MB) | | |
    0x1400+----------------------------------+ | rootfs |
    | u-boot.img (4 MB) | | |
    0x3400+----------------------------------+ | |
    | environment (128 KB) | | |
    0x3500+----------------------------------+ | |
    | backup environment (128 KB) | | |
    0x3600+----------------------------------+ +-------------------------+
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    But who creates the boot0 partition? Also those two commands are not supported by my uboot version. Do I need to enable addition KConfig values?

    Fullscreen
    1
    2
    => mmc partconf 0 1 1 1
    => mmc bootbus 0 2 0 0
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Dimitri M.
    TI__Expert 8410 points

    Hi Dimitri,

    You are using 9.0  FW: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.1--v09.00.01 (Kool Koala)')

    Lets try using only TI SDK version 08.06.

    The eMMC device will come with hardware Boot0 partition, hardware Boot1 partition, and UDA partition. The UDA is user defined, so you could create as many partitions you like in UDA.

    parconf and bootbbus should be supported by 08.06 TI SDK.

    If you  boot to Linux Kernel, you will see the partitions if you do the following commands:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    root@am62xx-evm:~# lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    mtdblock0 31:0 0 512K 0 disk
    mtdblock1 31:1 0 2M 0 disk
    mtdblock2 31:2 0 4M 0 disk
    mtdblock3 31:3 0 256K 0 disk
    mtdblock4 31:4 0 256K 0 disk
    mtdblock5 31:5 0 55.8M 0 disk
    mtdblock6 31:6 0 256K 0 disk
    mmcblk0 179:0 0 14.8G 0 disk
    |-mmcblk0p1 179:1 0 16M 0 part /run/media/mmcblk0p1
    `-mmcblk0p2 179:2 0 14.8G 0 part
    mmcblk0boot0 179:32 0 31.5M 1 disk
    mmcblk0boot1 179:64 0 31.5M 1 disk
    mmcblk1 179:96 0 14.6G 0 disk
    |-mmcblk1p1 179:97 0 133.6M 0 part /boot
    `-mmcblk1p2 179:98 0 2.7G 0 part /
    root@am62xx-evm:~#
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


    mmcblk0boot0 and mmcblk0boot1 are the hardware boot0 and boot1 partitions. I have created two partitions using fdisk in UDA for MMCSD (eMMC boot using UDA). :
    - mmcblk0p1
    - mmcblk0p2

    First I would check in Linux kernel what partitions you have. I believe USB DFU, by default, writes to eMMC hardware boot0 partition. So you could verify in Linux kernel it is there.

    ~ Judith