TDA4VPE-Q1: The TDA4VPE cannot bringup from DFU mode

Hi Zhongxin,

zhongxin zhou said:

step 1: The tda4vpe is configured to start in DFU mode, and connect the board to the PC using a USB cable

Can you help us with how did you configure it in DFU mode.

zhongxin zhou said:

step 2: Then, use the script to load the DFU files tiboot3.bin, tispl.bin, and u-boot.img in the Linux PC

Can you help us with the commands you used in the script while loading the DFU files.

Can you also share the boot logs with us as well as the SDK version  and path of the boot files you were using .

Regards

Gokul

Step 1: The hardware schematic diagram and physical connection diagram are as follows:

Step 2:  we execute command in Linux PC, the context of script file and the command output in linux PC are follows, and No output from Serial(COM 1):

Hi zhongxin,

• Are you using a custom board or TI J742s2 EVM?
• If it is a custom board, can you provide the hardware schematics of the USB.
• Can you also try following the steps in the below link and provide the logs and screenshots:
  • 3.1.1.2. USB Device Firmware Upgrade (DFU) — Processor SDK Linux for J742s2 Documentation

Regards

Gokul

We using custom board

The hardware schematics of the USB:

The DFU log of custom board:

Hi Zhongxin,

• Can you also try following the steps in the below link and provide the logs and screenshots:
  • 3.1.1.2. USB Device Firmware Upgrade (DFU) — Processor SDK Linux for J742s2 Documentation

Regards

Gokul

We use the SDK 11.00 Yocto build result of uboot(tiboot3.bin), it is OK on TI J742S2 EVM board(The COM terminal can enter the U-Boot CLI)

Hi Zhongxin,

So , the issue is with the custom board as it is working on TI EVM, I will inform the USB hardware expert to have a look into the USB schematics.

Thanks in advance for your patience.

Regards

Gokul

Comment from one of my colleague below: 

"Can we determine if tiboot3.bin has booted correctly? After tiboot3.bin is up, does the dfu-util -l show interfaces for sending firmware? "

Thank you for your reply.

We have confirmed that the root cause is: the DDR size of the EVM board is 16GB, but the DDR size of our custom board is 8GB, and I used the default DDR configuration in tiboot3.bin. Therefore, after our board executed tiboot3.bin, it reported a failed DDR handshake and then stopped.

After modifying the DDR configuration and rebuilding tiboot3.bin, the DFU boot worked normally