Tool/software:
Hi TI,
I refer to below link to generate tiboot3.bin, and flash it to EVM borad.
I used mcu_plus_sdk_am62ax_09_00_00_19, the device became HSSE after tiboot3 was burned.
The next step needs to start from emmc, how to burn the image to emmc? I have encountered a problem that the device cannot burn writing when entering dfu mode.
Detailed operations are as follows:
1. The evm enters the dfu mode
2. The pc burns the image with the following log:
lutao@ubuntu:/home/tony/Work/DSSAD/uboot-flash-writer/tools/DFU_flash/bin/am62axx-evm/hs$ 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 http://sourceforge.net/p/dfu-util/tickets/ Found DFU: [0451:6165] ver=0200, devnum=32, cfg=1, intf=0, path="3-4.1", alt=1, name="SocId", serial="01.00.00.00" Found DFU: [0451:6165] ver=0200, devnum=32, cfg=1, intf=0, path="3-4.1", alt=0, name="bootloader", serial="01.00.00.00" lutao@ubuntu:/home/tony/Work/DSSAD/uboot-flash-writer/tools/DFU_flash/bin/am62axx-evm/hs$ sudo dfu-util -R -a bootloader -D 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 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:6165 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% 359889 bytes Download done. state(6) = dfuMANIFEST-SYNC, status(0) = No error condition is present dfu-util: unable to read DFU status after completion Resetting USB to switch back to runtime mode
The serial port log of the evm board is as follows:
U-Boot SPL 2021.01 (Jun 21 2023 - 11:56:12 +0530) SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar') am62a_init: board_init_f done am62a_init: spl_boot_device: devstat = 0x53 bootmedia = 0xa bootindex = 0 SPL: Unsupported Boot Device! SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ###
3. After tiboot3.bin is burned, the pc executes "sudo dfu-util -l". No device can burn other images (tispl.bin and u-boot.img).
lutao@ubuntu:/home/tony/Work/DSSAD/uboot-flash-writer/tools/DFU_flash/bin/am62axx-evm/hs$ 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 http://sourceforge.net/p/dfu-util/tickets/
When the EVM device is in HSFS, the above 1 and 2 operations are completed. In step 3, the pc executes "sudo dfu-util -l", and a device similar to the following appears:
$ sudo dfu-util -l ... Found DFU: [0451:6165] ver=0224, devnum=12, cfg=1, intf=0, path="3-4.1.3", alt=1, name="u-boot.img", serial="UNKNOWN" Found DFU: [0451:6165] ver=0224, devnum=12, cfg=1, intf=0, path="3-4.1.3", alt=0, name="tispl.bin", serial="UNKNOWN"
In this way, you can continue to do tispl.bin and u-boot.img burn.
But, now is HSSE, and there is no equipment, can not proceed to the next burn.
How to solve the above problems? Can you help to check?
Thanks.
Tao
