PROCESSOR-SDK-J722S: Updating an eMMC using DFU is fail

Hi Maojiang,

Can you make the following changes , rebuild tiboot3.bin,tispl.bin and u-boot and try?

diff --git a/configs/j722s_evm_a53_defconfig b/configs/j722s_evm_a53_defconfig
index d4be8eaf0fc..30cb728fb15 100644
--- a/configs/j722s_evm_a53_defconfig
+++ b/configs/j722s_evm_a53_defconfig
@@ -10,6 +10,7 @@ CONFIG_TARGET_J722S_A53_EVM=y
 CONFIG_HAS_CUSTOM_SYS_INIT_SP_ADDR=y
 CONFIG_CUSTOM_SYS_INIT_SP_ADDR=0x80480000
 CONFIG_SF_DEFAULT_SPEED=25000000
+CONFIG_SYS_MALLOC_LEN=0x2000000
 CONFIG_ENV_SIZE=0x40000
 CONFIG_DM_GPIO=y
 CONFIG_SPL_DM_SPI=y

Regards

Gokul

Hi,Gokul

thank you for your respone and suggestion

you mentions the above changes, I have rebuild tiboot3.bin,tispl.bin and u-boot, the command "dfu 0 mmc 0" is work fine for me,but I have a new problem that dosen't boot from eMMC.

1.flashing images(tiboot3.bin,tispl.bin,u-boot and tisdk-base.ext4) to eMMC via dfu tool, it's show that all of things are work fine. as show below:

Target logs:

U-Boot SPL 2024.04-ti-dirty (Jul 02 2025 - 17:42:39 +0800)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.6--v10.01.06 (Fiery Fox)')
SPL initial stack usage: 17048 bytes
Trying to boot from DFU
###################################################DOWNLOAD ... OK
Ctrl+C to exit ...
Authentication passed
Authentication passed
Authentication passed
init_env from device 10 not supported!
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.11.0(release):v2.11.0-906-g58b25570c9-dirty
NOTICE:  BL31: Built : 04:20:32, Nov  1 2024

U-Boot SPL 2024.04-ti-dirty (Jul 02 2025 - 16:22:28 +0800)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.6--v10.01.06 (Fiery Fox)')
Trying to boot from DFU
#####DOWNLOAD ... OK
Ctrl+C to exit ...
Authentication passed
Authentication passed


U-Boot 2024.04-ti-dirty (Jul 02 2025 - 16:22:28 +0800)

SoC:   J722S SR1.0 HS-FS
Model: Texas Instruments J722S EVM
DRAM:  2 GiB (effective 8 GiB)
Core:  79 devices, 29 uclasses, devicetree: separate
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0
=>
=>
=>
=>
=>
=>
=> mmc part

Partition Map for MMC device 0  --   Partition Type: EFI

Part    Start LBA       End LBA         Name
        Attributes
        Type GUID
        Partition GUID
  1     0x00000022      0x03b47fde      "rootfs"
        attrs:  0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   85f758b6-5706-b244-9ce8-a53ea70173f5
=> gpt write mmc 0 ${partitions}
Writing GPT: success!
=> setenv dfu_alt_info ${dfu_alt_info_emmc}
=> dfu 0 mmc 0
##DOWNLOAD ... OK
Ctrl+C to exit ...
####DOWNLOAD ... OK
Ctrl+C to exit ...
#####DOWNLOAD ... OK
Ctrl+C to exit ...
################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################DOWNLOAD ... OK
Ctrl+C to exit ...
=> mmc partconf 0 1 7 1
=> mmc bootbus 0 2 0 0
Set to BOOT_BUS_WIDTH = 0x2, RESET = 0x0, BOOT_MODE = 0x0
=>

Host logs:

PS Z:\ti\dfu-boot\emmc-boot> 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 Runtime: [174f:1820] ver=1112, devnum=1, cfg=1, intf=4, path="4-1", alt=0, name="Camera DFU Device", serial="0001"
Found DFU: [0451:6165] ver=0223, devnum=8, cfg=1, intf=0, path="2-1.4", alt=6, name="sysfw.itb.raw", serial="UNKNOWN"
Found DFU: [0451:6165] ver=0223, devnum=8, cfg=1, intf=0, path="2-1.4", alt=5, name="u-env.raw", serial="UNKNOWN"
Found DFU: [0451:6165] ver=0223, devnum=8, cfg=1, intf=0, path="2-1.4", alt=4, name="u-boot.img.raw", serial="UNKNOWN"
Found DFU: [0451:6165] ver=0223, devnum=8, cfg=1, intf=0, path="2-1.4", alt=3, name="tispl.bin.raw", serial="UNKNOWN"
Found DFU: [0451:6165] ver=0223, devnum=8, cfg=1, intf=0, path="2-1.4", alt=2, name="tiboot3.bin.raw", serial="UNKNOWN"
Found DFU: [0451:6165] ver=0223, devnum=8, cfg=1, intf=0, path="2-1.4", alt=1, name="rootfs", serial="UNKNOWN"
Found DFU: [0451:6165] ver=0223, devnum=8, cfg=1, intf=0, path="2-1.4", alt=0, name="rawemmc", serial="UNKNOWN"
PS Z:\ti\dfu-boot\emmc-boot> dfu-util.exe -c 1 -i 0 -a 2 -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/

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 #2 ...
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%       370343 bytes
Download done.
DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
DFU state(2) = dfuIDLE, status(0) = No error condition is present
Done!
PS Z:\ti\dfu-boot\emmc-boot> dfu-util.exe -c 1 -i 0 -a 3 -D tispl.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/

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 #3 ...
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%      1034011 bytes
Download done.
DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
DFU state(2) = dfuIDLE, status(0) = No error condition is present
Done!
PS Z:\ti\dfu-boot\emmc-boot> dfu-util.exe -c 1 -i 0 -a 4 -D u-boot.img
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 #4 ...
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%      1210371 bytes
Download done.
DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
DFU state(2) = dfuIDLE, status(0) = No error condition is present
Done!
PS Z:\ti\dfu-boot\emmc-boot> dfu-util.exe -c 1 -i 0 -a 1 -D tisdk-base.ext4
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/

Invalid argument: Could only read 0 of 536870912 bytes from tisdk-base.ext4
PS Z:\ti\dfu-boot\emmc-boot> 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 Runtime: [174f:1820] ver=1112, devnum=1, cfg=1, intf=4, path="4-1", alt=0, name="Camera DFU Device", serial="0001"
Found DFU: [0451:6165] ver=0223, devnum=8, cfg=1, intf=0, path="2-1.4", alt=6, name="sysfw.itb.raw", serial="UNKNOWN"
Found DFU: [0451:6165] ver=0223, devnum=8, cfg=1, intf=0, path="2-1.4", alt=5, name="u-env.raw", serial="UNKNOWN"
Found DFU: [0451:6165] ver=0223, devnum=8, cfg=1, intf=0, path="2-1.4", alt=4, name="u-boot.img.raw", serial="UNKNOWN"
Found DFU: [0451:6165] ver=0223, devnum=8, cfg=1, intf=0, path="2-1.4", alt=3, name="tispl.bin.raw", serial="UNKNOWN"
Found DFU: [0451:6165] ver=0223, devnum=8, cfg=1, intf=0, path="2-1.4", alt=2, name="tiboot3.bin.raw", serial="UNKNOWN"
Found DFU: [0451:6165] ver=0223, devnum=8, cfg=1, intf=0, path="2-1.4", alt=1, name="rootfs", serial="UNKNOWN"
Found DFU: [0451:6165] ver=0223, devnum=8, cfg=1, intf=0, path="2-1.4", alt=0, name="rawemmc", serial="UNKNOWN"
PS Z:\ti\dfu-boot\emmc-boot> dfu-util.exe -c 1 -i 0 -a 1 -D tisdk-base.ext4
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 #1 ...
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%    536870912 bytes
Download done.
DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
DFU state(2) = dfuIDLE, status(0) = No error condition is present
Done!
PS Z:\ti\dfu-boot\emmc-boot>

2. dip switches change to boot from eMMC

• SW3[1:8] = 1101 0010 
• SW4[1:8] = 0000 0000

3.reboot TI evm board(hardware reset SW5)

4.there is not any log ibformation to output for my linux terminal

Can you please help to solve the error(above setp3) or give some suggestions

Regards

Maojiang

Hi Maojiang,

The dfu flashes the boot files to boot 0 partition of emmc as we only have support for that.

Hence you will have to have the following commands in u-boot:

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

Boot switch settings : To boot from Boot0 partition of eMMC.

SW3[1:8] = 11010011

SW4[1:8] = 00000000

Regards

Gokul

Hi,Gokul

thank you for your respone and suggestion

1. you mentions the above changes, I have already  tried, but, The result is still the same.

3. dip switches change to boot from eMMC

• SW3[1:8] = 1101 0011 
• SW4[1:8] = 0000 0000

3.there is not any log ibformation to output for my linux terminal after reboot TI evm board(hardware reset SW5).

the dfu_alt_info_mmc information is "alt_info_mmc=boot part 1 1; rootfs part 1 2; tiboot3.bin fat 1 1; tispl.bin fat 1 1; u-boot.img fat 1 1; uEnv.txt fat 1 1; sysfw.itb fat 1 1".

is't correct?

Can you please help to give some other suggestions

Hi Maojiang,

MAOJIANG YAO said:

there is not any log ibformation to output for my linux terminal after reboot TI evm board(hardware reset SW5).

the dfu_alt_info_mmc information is "alt_info_mmc=boot part 1 1; rootfs part 1 2; tiboot3.bin fat 1 1; tispl.bin fat 1 1; u-boot.img fat 1 1; uEnv.txt fat 1 1; sysfw.itb fat 1 1".

You have used alt_info_emmc right, not alt_info_mmc,right.

Can you mention where you are trying to take the boot files(tiboot3.bin,tispl.bin,u-boot.img) from?

Also can you share the file sizes of the boot files(tiboot3.bin,tispl.bin,u-boot.img)?

Regards

Gokul

Gokul Praveen said:

Regards

Hi,Gokul

You have used alt_info_emmc right, not alt_info_mmc,right.

yes,it's alt_info_emmc ,as show figure below:

   Can you mention where you are trying to take the boot files(tiboot3.bin,tispl.bin,u-boot.img) from?

   Also can you share the file sizes of the boot files(tiboot3.bin,tispl.bin,u-boot.img)?

,as show figure below:

Regards

Maojiang

Hi Maojiang,

Sorry for the delayed response.

Can you flash the files in your [PS Z:\ti\dfu-boot] into the eMMC as those files were booting fine using dfu boot.

Also can you share the output of the below command at u-boot command prompt:

printenv dfu_alt_info_emmc

Regards

Gokul

Hi,Gokul

thank you for your response.

Q1, Can you flash the files in your [PS Z:\ti\dfu-boot] into the eMMC as those files were booting fine using dfu boot.

after perform command the 'dfu 0 mmc 0", and than to flash the files in my[PS Z:\ti\dfu-boot] into the eMMC, Is this the operation that is required?

Q2,  Also can you share the output of the below command at u-boot command prompt:

printenv dfu_alt_info_emmc
dfu_alt_info_emmc=rawemmc raw 0 0x800000 mmcpart 1; rootfs part 0 1; tiboot3.bin.raw raw 0x0 0x400 mmcpar  t 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

=> printenv dfu_alt_info_emmc
dfu_alt_info_emmc=rawemmc raw 0 0x800000 mmcpart 1; rootfs part 0 1; 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
=> setenv dfu_alt_info ${dfu_alt_info_emmc}
=> printenv dfu_alt_info_emmc
dfu_alt_info_emmc=rawemmc raw 0 0x800000 mmcpart 1; rootfs part 0 1; 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
=> <INTERRUPT>
=>
=>
=>
=> printenv dfu_alt_info
dfu_alt_info=rawemmc raw 0 0x800000 mmcpart 1; rootfs part 0 1; 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

Regards

Maojiang

Hi Maojiang,

MAOJIANG YAO said:

after perform command the 'dfu 0 mmc 0", and than to flash the files in my[PS Z:\ti\dfu-boot] into the eMMC, Is this the operation that is required?

Yes Maojiang,

Also,can you use the below commands when flashing the boot files to the eMMC from the host.

>sudo dfu-util -l

>sudo dfu-util -a tiboot3.bin.raw -D <tiboot3.bin in PS Z:\ti\dfu-boot directory>

>sudo dfu-util -a tispl.bin.raw -D <tispl.bin in PS Z:\ti\dfu-boot directory>

>sudo dfu-util -a u-boot.img.raw -D <u-boot.imgin PS Z:\ti\dfu-boot directory>

Just one more question, Maojiang:

• From which path in the SDK directory are you taking the tiboot3.bin,tispl.bin and u-boot.img ?

Regards

Gokul

Hi,Gokul

thank you for your response.

following the setps,

1.building the ti-uboot project, The below command was performd ( add a config file "j722s_evm_r5_usbdfu.config"), and then will be generate new tiboot3.bin,tispl.bin and u-boot.img

    $(MAKE) -j $(MAKE_JOBS) -C $(UBOOT_SRC_DIR) ARCH=arm $(UBOOT_MACHINE_R5) j722s_evm_r5_usbdfu.config\
        O=$(UBOOT_R5_BUILD)        
    $(MAKE) -j $(MAKE_JOBS) -C $(UBOOT_SRC_DIR) ARCH=arm CROSS_COMPILE=$(CROSS_COMPILE_ARMV7) \
        BINMAN_INDIRS=$(TI_LINUX_FIRMWARE) \
        O=$(UBOOT_R5_BUILD)

2.dip swtitch change to boot from usb,and hardware reset

SW3[1:8] = 1100 1010  SW4[1:8] = 0000 0000

3. download images to j722S target board via dfu tool

3.1 host log

PS Z:\ti\dfu-boot> dfu-util.exe -c 1 -i 0 -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/

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
Device returned transfer size 512
Copying data from PC to DFU device
Download        [=========================] 100%       350591 bytes
Download done.
DFU state(6) = dfuMANIFEST-SYNC, status(0) = No error condition is present
unable to read DFU status after completion (LIBUSB_ERROR_PIPE)
PS Z:\ti\dfu-boot> dfu-util.exe -c 1 -i 0 -a tispl.bin -D tispl.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/

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
Device returned transfer size 4096
Copying data from PC to DFU device
Download        [=========================] 100%      1034011 bytes
Download done.
DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
DFU state(2) = dfuIDLE, status(0) = No error condition is present
Done!
PS Z:\ti\dfu-boot> dfu-util.exe -c 1 -i 0 -a u-boot.img  -D u-boot.img
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 #1 ...
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%      1210387 bytes
Download done.
DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
DFU state(2) = dfuIDLE, status(0) = No error condition is present
Done!
PS Z:\ti\dfu-boot>

3.2 target log

4. septs for target, as show below.

5.septs for host, as show below. flashing images to eMMC from host via DFU

NOTE: tiboot3.bin,tispl.bin and u-boot.img are same above step3

5.1 the below command was failed in the my folder "Z:\ti\dfu-boot>"

dfu-util.exe  -a tiboot3.bin.raw -D tiboot3.bin

5.2 So, I perform the below command to downlaod image to eMMC in the my folder "Z:\ti\dfu-boot>"

dfu-util.exe -c 1 -i 0 -a tiboot3.bin.raw -D tiboot3.bin

dfu-util.exe -c 1 -i 0 -a tispl.bin.raw -D tispl.bin

dfu-util.exe -c 1 -i 0 -a u-boot.img.raw  -D u-boot.img

5.2.1 host log

PS Z:\ti\dfu-boot> dfu-util.exe -c 1 -i 0 -a tiboot3.bin.raw -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/

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 #2 ...
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%       350591 bytes
Download done.
DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
DFU state(2) = dfuIDLE, status(0) = No error condition is present
Done!
PS Z:\ti\dfu-boot> dfu-util.exe -c 1 -i 0 -a tispl.bin.raw -D tispl.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/

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 #3 ...
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%      1034011 bytes
Download done.
DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
DFU state(2) = dfuIDLE, status(0) = No error condition is present
Done!
PS Z:\ti\dfu-boot> dfu-util.exe -c 1 -i 0 -a u-boot.img.raw  -D u-boot.img
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 #4 ...
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%      1210387 bytes
Download done.
DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
DFU state(2) = dfuIDLE, status(0) = No error condition is present
Done!

5.2.2 target log

6. set for target 

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

7.dip swtitch change to boot from eMMC

SW3[1:8] = 1101 0011  SW4[1:8] = 0000 0000

8. reboot TI evm board(hardware reset SW5)

9.there is not any log ibformation to output for my linux terminal

Regards

Maojiang

Hi,Gokul

there are similar issues regarding the eMMC boot as well.

1. I performd below command to dowaload images to eMMC

=> mmc dev 0 1
=> fatload mmc 1 ${loadaddr} tiboot3.bin
=> mmc write ${loadaddr} 0x0 0x400
=> fatload mmc 1 ${loadaddr} tispl.bin
=> mmc write ${loadaddr} 0x400 0x1000
=> fatload mmc 1 ${loadaddr} u-boot.img
=> mmc write ${loadaddr} 0x1400 0x2000

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

2. .dip swtitch change to boot from eMMC

SW3[1:8] = 1101 0011  SW4[1:8] = 0000 0000

3. reboot TI evm board(hardware reset SW5)

4.there is not any log ibformation to output for my linux terminal

Regards

Maojiang

HI Maojiang,

I tried the same on my end and it is working fine for me where it is booting from eMMC BOOT 0.

Logs:

• Can you provide the SDK version which you are using?
  • I tried with J722S SDK version 10_00_00_08.
• Can you try flashing with files[tiboot3.bin,tispl.bin and u-boot.img] present in <SDK_DIR>/board-support/prebuilt-images folder?

Regards

Gokul

Q1，Can you provide the SDK version which you are using?

Q2, Can you try flashing with files[tiboot3.bin,tispl.bin and u-boot.img] present in <SDK_DIR>/board-support/prebuilt-images folder?

1.

 I have tried flashing with files[tiboot3.bin,tispl.bin and u-boot.img] present in <SDK_DIR>/board-support/prebuilt-images folder,as show below

booting from sd-card is working fine for me, but  it is working fail for me where it is booting from eMMC BOOT 0,as show below.

2. .dip swtitch change to boot from eMMC after flashing image to eMMC, as above figure below. 

SW3[1:8] = 1101 0011  SW4[1:8] = 0000 0000

3. reboot TI evm board(hardware reset SW5)

4.there is not any log ibformation to output for my linux terminal

Regards

Maojiang

Hi Maojiang,

I tried the same on 10.01.00.04 and it works on my end.

Logs:

Can you ensure the following :

SW3[1:8] = 1101 0011 

SW4[1:8] = 0000 0000

SW2[1:8] = 00011100

Also,can you make sure you are connecting to the 3rd instance of UART(ttyUSB2) for seeing the logs.

MAOJIANG YAO said:

3. reboot TI evm board(hardware reset SW5)

Replug the power cable instead of hardware reset.

Regards

Gokul

Hi,Gokul

thank you for your respone,

I build a new u-boot, it doesn't work after rebooting TI evm board(hardware reset SW5),but  it works fine when booting from the eMMC after re-powering the TI evm board, there are similar issues regarding the 10.01.00.04 as well..

following the setps,

1. logs

2. .dip swtitch change to boot from eMMC after flashing image to eMMC, as above figure below. 

SW3[1:8] = 1101 0011  SW4[1:8] = 0000 0000 SW2[1:8] = 00011100

3.reboot TI evm board

3.1 hardware reset SW5,there is not any log ibformation to output for my linux terminal

3.2 re-powering via type-C(J24), it works fine when booting from the eMMC after re-powering the TI evm board,as show below

4. I take a picture of the TI evm board.

Regards

Maojiang

Hi Maojiang,

Thanks for the confirmation. Actually the  boot switches we set on the board sets the DEV_STAT register based on which the BOOTROM fetches which boot media to take boot files from.

However, the DEV STAT register does not get updated when doing hardware reset using SW5. Hence, if the boot switches have to be changed(ie:the boot media has to be changed),you will have to power off and power on the board.

However,if the you want to reset the board without changing the boot media,hardware reset(SW5) will work fine.

Regards

Gokul

Hi,Gokul
thank you for your suggestion,

I'm still a little confused about  booting from eMMC partition 0.

following the setps,

1.dip swtitch change to boot from eMMC after flashing image to eMMC, as above steps. 

SW3[1:8] = 1101 0011  SW4[1:8] = 0000 0000 SW2[1:8] = 00011100

2.power-on the board of J722S 

it's works fine for me,as show below.

3. don't change the power supply state and the boot switches, after hardware reset SW5 there is not any log ibformation to output for my linux terminal,

 Is it correct?

Regards

Maojiang

Hi Maojiang.

What you have stated is perfectly correct.

The only thing is power cycle the board after flashing files to eMMC. Do not do hardware reset using SW5 as it is having issues and we will report this to the hardware team as well regarding SW5 issue.

Basically, in short the steps are:

• Flash files to eMMC boot0
• power off the board
• change the boot switch settings to boot from eMMC boot 0 partition.
• Power on the board.

Regards

Gokul