TDA4VP-Q1: HS-FS USB-Bootmode: DFU device is lost after tiboot transfer

Part Number: TDA4VP-Q1

Tool/software:

Dear TI-experts,

I am currently facing a similar issue as in this TI E2E thread.

I can boot the TDA4VP HS-FS SoC in UART and USB Bootmode just fine. However, after DFU-downloading the `tiboot3-j784s4-hs-fs-evm.bin` to the TDA4, the USB-DFU connection is lost and I am getting no MCU_UART output.

I have the same error with ti-processor-sdk-linux-adas-j784s4-evm-10_01_00_05 and ti-processor-sdk-linux-adas-j784s4-evm-11_00_00_08.

Uploading the SocId via USB-DFU is possible:

UART Bootmode is also working fine. This is the output:

02000000011a00006a376165700000000000000048534653000801000008010002a60000000000002b28ecde967b79d61619f89cf299205c36d179cacb2b1c5a7f16e3169cc879602122d07ad47ae878a46e243c6f5078c04a5452faceeccb00d0453a5a5e6420daad0bc40b0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000cbe311e91764a696d5dd1d2591181d08cb1c2c7bc62e0a2c90f14b38fbbef7dC

What could be the cause of this issue? How can I try to resolve this error?

Best regards,

Andreas

  • Hi Andreas,

    I can boot the TDA4VP HS-FS SoC in UART and USB Bootmode just fine. However, after DFU-downloading the `tiboot3-j784s4-hs-fs-evm.bin` to the TDA4, the USB-DFU connection is lost and I am getting no MCU_UART output

    The logs would ideally come in main uart . Please can you check the logs there.

    Also can you share the output of the command "sudo dfu-util -l " after sending the tiboot3.file.

    Regards

    Gokul

  • Hi Gokul,

    I connected the main UART, but I don't see any output.

    This is the complete dfu-util output:

    $ dfu-util -l
    dfu-util 0.9
    
    Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
    Copyright 2010-2016 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:6167] ver=0200, devnum=5, cfg=1, intf=0, path="1-1", alt=1, name="SocId", serial="01.00.00.00"
    Found DFU: [0451:6167] ver=0200, devnum=5, cfg=1, intf=0, path="1-1", alt=0, name="bootloader", serial="01.00.00.00"
    
    $ dfu-util -R -a bootloader -D board-support/ti-u-boot-2024.04+git/build/r5/tiboot3-j784s4-hs-fs-evm.bin
    dfu-util 0.9
    
    Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
    Copyright 2010-2016 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: Invalid DFU suffix signature
    dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
    Opening DFU capable USB device...
    ID 0451:6167
    Run-time device DFU version 0110
    Claiming USB DFU Interface...
    Setting Alternate Setting #0 ...
    Determining device status: state = dfuIDLE, status = 0
    dfuIDLE, continuing
    DFU mode device DFU version 0110
    Device returned transfer size 512
    Copying data from PC to DFU device
    Download	[=========================] 100%       478515 bytes
    Download done.
    state(6) = dfuMANIFEST-SYNC, status(0) = No error condition is present
    state(2) = dfuIDLE, status(0) = No error condition is present
    Done!
    dfu-util: can't detach
    Resetting USB to switch back to runtime mode
    $ dfu-util -l
    dfu-util 0.9
    
    Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
    Copyright 2010-2016 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/
    

    Best regards,

    Andreas

  • Hi Gokul,

    some additional information: I had to change the UART pinmux, because it is connected different compared to the EVM board.

    After I swapped to the MCU_UART0 as stdout, I got this output:

    U-Boot SPL 2024.04-ti-dirty (Sep 09 2025 - 10:08:00 +0200)
    SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.6--v10.01.06 (Fiery Fox)')
    Timeout during frequency handshake
    ### ERROR ### Please RESET the board ###

    What could be the cause of this problem? Also, is there a way to get additional debug output?

    Best regards,

    Andreas

  • HI Andreas,

    Can you share the boot logs after booting through UART BOOT mode.

    Regards

    Gokul

  • Hi Gokul,

    when trying to transfer the tiboot.bin through UART Bootmode, the minicom xmodem transfer only receives NACKs. I think this might be a different problem, that's not really worth looking into.

    The UART output I shared before already gives the hint that the DDR configuration from DDRSS RegConfigTool must be updated.

    Would you agree?

    Regards,

    Andreas

  • Hi Gokul,

    I was able to initialize the DRAM by removing the third DRAM controller, because the board only has 3 DRAM controllers in use:

    U-Boot SPL 2025.01-ti-g70667128cb5b-dirty (Sep 09 2025 - 13:18:59 +0200)
    SYSFW ABI: 4.0 (firmware rev 0x000b '11.0.9--v11.00.09+ (Fancy Rat)')
    Initialized 3 DRAM controllers
    SPL initial stack usage: 13456 bytes
    Trying to boot from DFU

    I will close this issue, but found a different issue where the ATF cannot be started on the A72 and opened a ticket for that topic.

    Regards,

    Andreas