AM6442: emmc layout + adding additional files to DFU flashing

Hello,

For flashing any image, you just have to give the image path and the flash offset in the config file. The flashing procedure is generic & is not tied to any specific images.

Regards,

Prashant

Hello TI,

Please let me know what can go wrong here, and is this the correct config file where i am making changes,

1. Iam using windows DFU tool

2. in the path "dfu-util-0.11-binaries\dfu-util-0.11-binaries\win64" there is cfg file called "flash-files.cfg" where i am adding below contents

# M4 multicore image @Raw
--file="hello_world_am64x-evm_m4fss0-0_nortos_ti-arm-clang.appimage.hs_fs" --operation=flash-emmc --flash-offset=0x800000 --attributes="raw,1,-"

# A53 multicore image @Raw
--file="linux.appimage.hs_fs" --operation=flash-emmc --flash-offset=0xA00000 --attributes="raw,1,-"

3. binaries i am keeping in the same path where "flash-files.cfg" is present

4. when i put my device to DFU mode and check for the list, Iam not seeing anything what iam added in .cfg file

D:\Projects\OSM\Tools\dfu-util-0.11-binaries\dfu-util-0.11-binaries\win64>dfu-util.exe --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 sourceforge.net/.../

Found DFU: [0451:6165] ver=0224, devnum=31, cfg=1, intf=0, path="1-3", alt=5, name="u-env.raw", serial="0000000000000000"
Found DFU: [0451:6165] ver=0224, devnum=31, cfg=1, intf=0, path="1-3", alt=4, name="u-boot.img.raw", serial="0000000000000000"
Found DFU: [0451:6165] ver=0224, devnum=31, cfg=1, intf=0, path="1-3", alt=3, name="tispl.bin.raw", serial="0000000000000000"
Found DFU: [0451:6165] ver=0224, devnum=31, cfg=1, intf=0, path="1-3", alt=2, name="tiboot3.bin.raw", serial="0000000000000000"
Found DFU: [0451:6165] ver=0224, devnum=31, cfg=1, intf=0, path="1-3", alt=1, name="rootfs", serial="0000000000000000"
Found DFU: [0451:6165] ver=0224, devnum=31, cfg=1, intf=0, path="1-3", alt=0, name="rawemmc", serial="0000000000000000"

Is the procedure what iam following is correct? please find the attached error logs

D:\Projects\OSM\Tools\dfu-util-0.11-binaries\dfu-util-0.11-binaries\win64>dfu-util.exe --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=0224, devnum=12, cfg=1, intf=0, path="1-3", alt=5, name="u-env.raw", serial="0000000000000000"
Found DFU: [0451:6165] ver=0224, devnum=12, cfg=1, intf=0, path="1-3", alt=4, name="u-boot.img.raw", serial="0000000000000000"
Found DFU: [0451:6165] ver=0224, devnum=12, cfg=1, intf=0, path="1-3", alt=3, name="tispl.bin.raw", serial="0000000000000000"
Found DFU: [0451:6165] ver=0224, devnum=12, cfg=1, intf=0, path="1-3", alt=2, name="tiboot3.bin.raw", serial="0000000000000000"
Found DFU: [0451:6165] ver=0224, devnum=12, cfg=1, intf=0, path="1-3", alt=1, name="rootfs", serial="0000000000000000"
Found DFU: [0451:6165] ver=0224, devnum=12, cfg=1, intf=0, path="1-3", alt=0, name="rawemmc", serial="0000000000000000"

D:\Projects\OSM\Tools\dfu-util-0.11-binaries\dfu-util-0.11-binaries\win64>
D:\Projects\OSM\Tools\dfu-util-0.11-binaries\dfu-util-0.11-binaries\win64>dfu-util.exe -S 0000000000000000 -a rawemmc -D hello_world_am64x-evm_m4fss0-0_nortos_ti-arm-clang.appimage.hs_fs -s 0x800000
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/

Warning: Invalid DFU suffix signature
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
Warning: DfuSe option used on non-DfuSe device
Device returned transfer size 4096
Could not read name, sscanf returned 0
Failed to parse memory layout for alternate interface 0

D:\Projects\OSM\Tools\dfu-util-0.11-binaries\dfu-util-0.11-binaries\win64>

Thank you,

Prathibha

Hello,

Prathibha S N said:

4. when i put my device to DFU mode and check for the list, Iam not seeing anything what iam added in .cfg file

How are you booting to A53 U-Boot over DFU?

Regards,

Prashant

Hello TI,

We are using boot selection switch to put the device in DFU, and we will load tiboot3.bin, tispl.bin and u-boot.img using below commands,

DFU on Windows
----------------
dfu-util.exe -S 01.00.00.00 -R -a bootloader -D tiboot3.bin
dfu-util.exe -S UNKNOWN -R -a tispl.bin -D tispl.bin
dfu-util.exe -S UNKNOWN -R -a u-boot.img -D u-boot.img

On device serial port we are using commands to boot the A53 in DFU,

---------------------

Uboot# gpt write mmc 0 ${partitions}          => this is to partition the eMMC
Uboot# setenv dfu_alt_info ${dfu_alt_info_emmc}          => this is to enable DFU
Uboot# dfu 0 mmc 0            => select eMMC 0

But the new files added in "flash-files.cfg" is not reflecting on command promt, Please let us know if this is the correct file? and the correct way of adding?

Are we missing anything in the procedure

Thank you,

Prathibha