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.

J721S2XSOMXEVM: When the board is configured as USB bootmode, dfu utils - l cannot recognize the device

Part Number: J721S2XSOMXEVM

Hi,

When the EVM board is configured as USB bootmode, using USB to plug into the TYPE-C (J5) port on the board. When the board is powered on, there is no response from the Win10 PC device manager. When using the dfu utils - l command on the terminal, no dfu devices can be recognized. Is it because PROC118E2 (001)_ U13B DNI in SCH.pdf?

Refer to the following document,j721s2 evm supports DFU.

  • HI Nancy 

    Are you testing this on evm?

    make sure your DFU mode is properly configured as shown below 

    reference : www.ti.com/.../spracy5.pdf

    i tested on a ubuntu setup its working 

    sudo dfu-util -l

    Found DFU: [0451:6168] ver=0200, devnum=27, cfg=1, intf=0, path="1-5.3", alt=1, name="SocId", serial="01.00.00.00"
    Found DFU: [0451:6168] ver=0200, devnum=27, cfg=1, intf=0, path="1-5.3", alt=0, name="bootloader", serial="01.00.00.00"

    Regards
    Diwakar

  • Yes, he tested both on EVM and his sample board. The DFU function can be realized on his sample board.

    Will it be related to the version of the board? Which version are you using?

  • Hi,

    Costomer confirmed that the DFU mode configuration is correct. He tests on PCB#:PROC118E2,Is it because of a version issue?

  • Hi Nancy 

    Will it be related to the version of the board? Which version are you using?

    i am using PROC079E3.

    In which version of board its failing ?

    Regards
    Diwakar

  • Hi,

    In which version of board its failing ?

    It's E2.

    U13B design is different on E2/E3.

  • Hi Nancy 

    I dont have E2 at my end lets loop in HW engineer to comment on this.

    Regards
    Diwakar

  • Nancy,

    Did you set up the USB in device mode in the EVMs to be recognized?

  • Costomer confirmed that the DFU mode configuration is correct. He tests on PCB#:PROC118E2,Is it because of a version issue?

    The bootmode is showed in the picture.

  • The USB mode looks to be set incorrectly.   I believe should be set to UFP for USB Boot.

  • Hi Robert,

    They can confirm it was configured with the following mode:

    On their A sample board, the DFU device is recognized, but after the download the bootloader, there is not DFU device. The operation and log are as follows: 

    Thanks and regards,

    Cherry

  • Hi Cherry 

    On their A sample board, t

    What do you mean bu A sample board do they have  other sample as well ?

    Are they able to boot with the other sample using same images ?

    Which sdk they are using ?

    Regards
    Diwakar

  • Hi Diwakar,

    What do you mean bu A sample board do they have  other sample as well ?

    They have two types of boards. One is our EVM, J721S2XSOMXEVM, after configured it to DFU mode boot, the USB does not react.

    The other is their A sample board, after configured it to DFU mode and boot, it will show "after the download of the bootloader, the DFU device is gone."

    Thanks and regards,

    Cherry 

  • Hi Cherry 

    The other is their A sample board, after configured it to DFU mode and boot, it will show "after the download of the bootloader, the DFU device is gone."

    Thanks for providing the information 

    Which sdk are you using for this ?

    Regards
    Diwakar

  • Hi Diwakar,

    Which sdk are you using for this ?

    ti-processor-sdk-linux-j721s2-evm-08_06_00_10 is being used now and they also tried to use ti-processor-sdk-linux-j721s2-evm-08_05_00_08, but it still failed.

    Thanks and regards,

    Cherry

  • Hi Cherry 

    I tried on evm i am able to boot using dfu boot mode in both of the sdk 

    j721s2-evm-08_05_00_08

    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:6168] ver=0200, devnum=17, cfg=1, intf=0, path="1-5.3", alt=1, name="SocId", serial="01.00.00.00"
    Found DFU: [0451:6168] ver=0200, devnum=17, cfg=1, intf=0, path="1-5.3", alt=0, name="bootloader", serial="01.00.00.00"
    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:6168
    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%       405751 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 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:6168
    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 4096
    Copying data from PC to DFU device
    Download	[=========================] 100%       945400 bytes
    Download done.
    state(7) = dfuMANIFEST, status(0) = No error condition is present
    state(2) = dfuIDLE, status(0) = No error condition is present
    Done!
    Resetting USB to switch back to runtime mode
    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:6168
    Run-time device DFU version 0110
    Claiming USB DFU Interface...
    Setting Alternate Setting #1 ...
    Determining device status: state = dfuIDLE, status = 0
    dfuIDLE, continuing
    DFU mode device DFU version 0110
    Device returned transfer size 4096
    Copying data from PC to DFU device
    Download	[=========================] 100%      1114964 bytes
    Download done.
    state(7) = dfuMANIFEST, status(0) = No error condition is present
    state(2) = dfuIDLE, status(0) = No error condition is present
    Done!
    Resetting USB to switch back to runtime mode
    

    ti-processor-sdk-linux-j721s2-evm-08_06_00_10

    fu-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:6168] ver=0200, devnum=20, cfg=1, intf=0, path="1-5.3", alt=1, name="SocId", serial="01.00.00.00"
    Found DFU: [0451:6168] ver=0200, devnum=20, cfg=1, intf=0, path="1-5.3", alt=0, name="bootloader", serial="01.00.00.00"
    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:6168
    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%       443574 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 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:6168
    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 4096
    Copying data from PC to DFU device
    Download	[=========================] 100%       984576 bytes
    Download done.
    state(7) = dfuMANIFEST, status(0) = No error condition is present
    state(2) = dfuIDLE, status(0) = No error condition is present
    Done!
    Resetting USB to switch back to runtime mode
    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:6168
    Run-time device DFU version 0110
    Claiming USB DFU Interface...
    Setting Alternate Setting #1 ...
    Determining device status: state = dfuIDLE, status = 0
    dfuIDLE, continuing
    DFU mode device DFU version 0110
    Device returned transfer size 4096
    Copying data from PC to DFU device
    Download	[=========================] 100%      1165976 bytes
    Download done.
    state(7) = dfuMANIFEST, status(0) = No error condition is present
    state(2) = dfuIDLE, status(0) = No error condition is present
    Done!
    Resetting USB to switch back to runtime mode
    

    The other is their A sample board, after configured it to DFU mode and boot, it will show "after the download of the bootloader, the DFU device is gone."

    i am assuming you haven't made any changes in the code and just trying to default images.

    Regards
    Diwakar

  • Hi Diwakar,

    i am assuming you haven't made any changes in the code and just trying to default images.

    Yes, you are correct.

    Could you help share the instructions you entered when you did the test on the EVM? Or is there any guidance to start? 

    Thanks and regards,

    Cherry 

  • Hi Cherry 

    I just made switch setting like 

    and then ran these commands.

    sudo dfu-util -l
    sudo dfu-util -R -a bootloader -D tiboot3.bin
    sudo dfu-util -R -a tispl.bin -D tispl.bin
    sudo dfu-util -R -a u-boot.img -D u-boot.img
    
    

    Regards
    Diwakar

  • Hi Diwakar,

    There might be something wrong with the customer's tiboot3.bin for their PCB board. So they wanted to debug tiboot.bin with uboot spl source code, they try to enable uart log output using WKUP_UART0, but failed. Is there any doc regarding how to debug tiboot3.bin using uart or Laudbach JTAG available?

    Thanks and regards,

    Cherry

  • Hi Cherry 

    Is customer have different ref Clock in  EVM we have 19.2MHz clock. ?

    Regards
    Diwakar

  • Hi Diwakar,

    ref Clock in  EVM we have 19.2MHz clock. ?

    Are you referring to the clock that is connected to the TDA4 H28/J28 port? If yes, here is the customer's clock, 26MHZ:

    It's different from EVM's:

    Thanks and regards,

    Cherry

  • HI Cherry 

    If the customer is using different PLL Ref clock they need to modify the same in their DTSI as well.

    change this to 26MHZ  in file k3-j721s2-r5-common-proc-board.dts build the uboot and copy the images to the boot partition

    I am assuming they already made a corresponding changes in the BOOTPINS that is why they are able to flash tiboot3.bin.

    Regards
    Diwakar