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.

J721EXSOMXEVM: DFU update failed with SDK 7.0

Part Number: J721EXSOMXEVM
Other Parts Discussed in Thread: UNIFLASH

Hello,

We have received several J721e based custom boards from the factory. I was able to flash the firmware in several boards over USB using "dfu-util" and the board is booting up fine from eMMC. 

We have one single board where I can flash "tiboot3.bin" & "sysfw.itb" but after this I don't see any output from "sudo dfu-util -l". That means I can't flash the rest of the bootloader. Here is the log - 

slaldas@daimler:~$ sudo dfu-util -R -a bootloader -D /home/slaldas/nova_slot5/build/arago-tmp-external-arm-glibc/deploy/images/nova-slot5/tiboot3.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 sourceforge.net/.../

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:6163
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%       229546 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

slaldas@daimler:~$ 
slaldas@daimler:~$ sudo 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 sourceforge.net/.../

Found DFU: [0451:6163] ver=0224, devnum=68, cfg=1, intf=0, path="1-3.2", alt=0, name="sysfw.itb", serial="UNKNOWN"

slaldas@daimler:~$ 
slaldas@daimler:~$ sudo dfu-util -R -a sysfw.itb -D /home/slaldas/nova_slot5/build/arago-tmp-external-arm-glibc/deploy/images/nova-slot5/sysfw.itb 
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 sourceforge.net/.../

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:6163
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%       268410 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

slaldas@daimler:~$ 
slaldas@daimler:~$ sudo 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 sourceforge.net/.../

Could you please let me know how to debug this issue?

Thanks,

Satish

  • Hi Satish,

    So essentially with the same boot switch setting, same commands and same USB cable you see different behavior on two different customer boards?

    Are the boards of the same revision? Or is there a delta between them?

    If no, then do you expect a HW issue here?

    Regards,

    Karan

  • Hi Karan,

    I have a bench setup and I simply change the boards when I flash the board. The rest of the accessories i.e. Power cable, USB cable, etc. stays the same. I flashed few more boards after I detected this issue with the same setup and they worked fine.

    Are the boards of the same revision? Or is there a delta between them?

    >>> It is the same revision, no variation in the board. The mystery is, It allows me to flash the first two bootloaders and then breaks. Is there a way to extract some debug logs from "tiboot3.bin" & "sysfw.itb"?

    If no, then do you expect an HW issue here?

    >>> We are trying to find a way to debug and corner the issue.

    Thanks,

    Satish

  • Hi Satish,

    Satish Lal Das2 said:
    Is there a way to extract some debug logs from "tiboot3.bin" & "sysfw.itb"?

    1. Do you mean more logs when flashing from DFU?

    2. Can you set the environment to default on the faulty board too? Do that by running "env default -f -a" followed by "saveenv" on the u-boot console.

    3. Is this only one board where you are seeing this issue?

    Regards,

    Karan

  • Hi Karan,

    Sorry for the delay in my reply.

    Unfortunately, I can't run those uboot commands as the flashing brakes right after flashing sysfw.itb. 

    1. Do you mean more logs when flashing from DFU?

    >>> I mean to say to find any logs which breaks the flashing sequence.

    3. Is this only one board where you are seeing this issue?

    >>> So far I flashed six-seven boards and this board is the only one preventing us from flashing. 

    Do you know if we can load these images via JTAG?

  • Hi Satish,

    You can take a look at using UNIFLASH to flash the eMMC - https://e2e.ti.com/support/processors/f/processors-forum/941068/ccs-tda4vmxevm-tda4vm-flash-emmc-using-uniflash/3477455#3477455 

    Do you know if we can load these images via JTAG?

    JTAG along with u-boot can be used to flash the binaries but with the current tools, JTAG alone can not be used to flash to eMMC. Is there another boot mode that works on the faulty board?

    Regards,

    Karan

  • Hi Karan,

    OSPI & eMMC are the boot media we have on our IVP board. I am enquiring from the Hardware team to see if they can populate SD card from this dead board. I am waiting for their response.

    Thanks,

    Satish