• State
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 12 replies
  • Subscribers 100 subscribers
  • Views 2295 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM623: Flashing tiboot3.bin using dfu-util

Lie Koon Kee
Prodigy 80 points

Part Number: AM623
Other Parts Discussed in Thread: SK-AM62

Hi TI,

Hi, as seen in the following, I have issue flashing tiboot3.bin into my processor. I'm in DFU boot mode trying to flash the first tiboot3.bin into the processor following e2e.ti.com/.../faq-sk-am62-how-to-flash-emmc-using-usb-dfu-on-am62x-sk-e2

koonklie@virtual-machine:~$ sudo dfu-util -l
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 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-2.1", alt=1, name="SocId", serial="01.00.00.00"
Found DFU: [0451:6165] ver=0200, devnum=32, cfg=1, intf=0, path="3-2.1", alt=0, name="bootloader", serial="01.00.00.00"
koonklie@virtual-machine:~$ sudo dfu-util -R -a bootloader -D /tmp/tiboot2/tiboot3.bin 
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 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: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
Opening DFU capable USB device...
Device ID 0451:6165
Device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 0110
Device returned transfer size 512
Copying data from PC to DFU device
Download	[=========================] 100%       335765 bytes
Download done.
DFU state(6) = dfuMANIFEST-SYNC, status(0) = No error condition is present
dfu-util: unable to read DFU status after completion (LIBUSB_ERROR_IO)
koonklie@virtual-machine:~$ sudo dfu-util -l
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 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=33, cfg=1, intf=0, path="3-2.1", alt=1, name="SocId", serial="01.00.00.00"
Found DFU: [0451:6165] ver=0200, devnum=33, cfg=1, intf=0, path="3-2.1", alt=0, name="bootloader", serial="01.00.00.00"
koonklie@virtual-machine:~$ sudo dfu-util -R -a bootloader -D /tmp/tiboot2/tiboot3.bin 
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 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: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
Opening DFU capable USB device...
Device ID 0451:6165
Device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 0110
Device returned transfer size 512
Copying data from PC to DFU device
Download	[=========================] 100%       335765 bytes
Download done.
DFU state(6) = dfuMANIFEST-SYNC, status(0) = No error condition is present
dfu-util: unable to read DFU status after completion (LIBUSB_ERROR_TIMEOUT)
koonklie@virtual-machine:~$ sudo dfu-util -l
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 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: Failed to retrieve language identifiers
dfu-util: Failed to retrieve language identifiers
dfu-util: Failed to retrieve language identifiers
dfu-util: Failed to retrieve language identifiers
Found DFU: [0451:6165] ver=0200, devnum=33, cfg=1, intf=0, path="3-2.1", alt=1, name="UNKNOWN", serial="UNKNOWN"
Found DFU: [0451:6165] ver=0200, devnum=33, cfg=1, intf=0, path="3-2.1", alt=0, name="UNKNOWN", serial="UNKNOWN"

My board is a custom board using AM6232. The same tiboot3.bin was used all the while when I was still using AM6234, I started facing this problem when I'm switching to AM6232. Do I need to rebuild this tiboot3.bin? What kind of changes do I need to do?

Thanks,

Koon Kee

  • 0
    Prodigy 80 points

    The tiboot3.bin I had was built using tisdk 8.04. While waiting for an answer, I'm trying to build another tiboot3.bin using the latest tisdk 9.0 following the steps here https://dev.ti.com/tirex/explore/content/linux-academy-AM62X-8.3.0.0.v1/ch-develop/dev-build-uboot.html#dev-build-uboot .

    I used the same step when I built the tiboot3.bin for tisdk 8.04 about a year ago, so I know it must be working. However, I noticed tisdk 9.0 has no k3-image-gen-<version> folder.

    Please support.

    Thanks,

    Koon Kee

  • 0 in reply to Lie Koon Kee
    TI__Guru**** 180506 points

    Hi Koon,

    Lie Koon Kee said:
    The same tiboot3.bin was used all the while when I was still using AM6234, I started facing this problem when I'm switching to AM6232. Do I need to rebuild this tiboot3.bin? What kind of changes do I need to do?

    I am not aware of any software change needed between am6234 and am6232.

    Lie Koon Kee said:
    However, I noticed tisdk 9.0 has no k3-image-gen-<version> folder.

    Yes, since SDK9.0, k3-image-gen has been replaced with binman in uboot. Please follow the instruction in AM62x Academy 9.0.0.0 v1 to build U-Boot in SDK9.0. I don't have access to dev.ti.com right now to point you to the Academy link. If you cannot find it, I will provide the link tomorrow once I am in office.

  • 0 in reply to Bin Liu
    Prodigy 80 points

    Hi Bin,

    I found this: https://dev.ti.com/tirex/explore/node?node=A__AT2YHZ2xvBafxJHgUwFZFw__linux_academy_am62x__XaWts8R__LATEST

    I tried to build dfu tiboot3.bin following the guide with slight change (changing am62x_evm_r5_defconfig to am62x_evm_r5_usbdfu_defconfig), refer to the code block below for the details. 

    $ export PATH=$PATH:/home/$USER/ti-processor-sdk-linux-am62xx-evm-09.00.00.03/external-toolchain-dir/arm-gnu-toolchain-11.3.rel1-x86_64-aarch64-none-linux-gnu/bin
$ cd /home/$USER/ti-processor-sdk-linux-am62xx-evm-09.00.00.03/board-support/ti-u-boot
$ export ARCH=arm
$ export CROSS_COMPILE=arm-none-linux-gnueabihf-
$ make am62x_evm_r5_usbdfu_defconfig O=build/r5
$ make -j8 BINMAN_INDIRS=$(pwd)../prebuilt-images O=build/r5

    I found the tiboot3-am62x-gp-evm.bin in /home/koonklie/ti-processor-sdk-linux-am62xx-evm-09.00.00.03/board-support/ti-u-boot/build/r5. However, it's still not usable.

    Thanks,

    Koon Kee

  • 0 in reply to Lie Koon Kee
    TI__Guru**** 180506 points

    Hi Koon,

    Here is a quick way to build uboot in SDK 9.0:

    Modify Rules.make at the SDK top level directory, change

        UBOOT_MACHINE_R5=am62x_evm_r5_defconfig

    to

        UBOOT_MACHINE_R5=am62x_evm_r5_usbdfu_defconfig

    then run command 'make u-boot' at the SDK top level directory.

  • 0 in reply to Bin Liu
    Prodigy 80 points

    Hi Bin,

    I followed your guides, modifying Rules.make, running make u-boot command, found a new folder called "u-boot-build" in board-support and found 3 different tiboot3 related bin files in /home/$USER/ti-processor-sdk-linux-am62xx-evm-09.00.00.03/board-support/u-boot-build/r5:

    1. tiboot3-am62x-gp-evm.bin

    2. tiboot3-am62x-hs-evm.bin

    3. tiboot3-am62x-hs-fs-evm.bin

    All 3 of them are not working.

    Do you have any tiboot3.bin for DFU that is working? (Not the one in the prebuilt images folder as that one is for emmc)

    Thanks,

    Koon Kee

  • 0 in reply to Lie Koon Kee
    Prodigy 80 points

    Hi Bin,

    I just tested two more things.

    1. Use the tiboot3-am62x-gp-evm.bin mentioned above which was built using UBOOT_MACHINE_R5=am62x_evm_r5_usbdfu_defconfig on SK-AM62 eval kit. I can proceed to flash tispl.bin and u-boot.img,  without problem. Same test was done on my previous custom board with processor AM6234ATGGHAALW and it works as well.

    However it doesn't work on my new custom board with processor AM6232ASGGHAALW. I wonder if anything special about this new processor that is stopping it from working?

    2. I found tisdk-default-image-am62xx-evm.wic.xz in /home/$USER/ti-processor-sdk-linux-am62xx-evm-09.00.00.03/filesystem/am62xx-evm, flashed it into SD card**, boot the board to U-Boot, switch to emmc dfu mode, flash tiboot3.bin, tispl.bin, u-boot.img (these 3 files from the prebuilt-images folder) and ext4 made from tisdk-base-image-am62xx-evm.tar.xz found from the filesystem folder as well into emmc, the new board boots from EMMC!

    Then I did the same thing again, but this time using tiboot3.bin, tispl.bin and u-boot.img that were built using make u-boot command. But no response in the serial console again when I boot using emmc boot mode. I wonder why? What's the difference between the tiboot3.bin in the prebuilt-images folder and the one that I built using make u-boot command?

    Below are the detailed steps. (Assuming EMMC is partitioned properly)

        a. Using UBOOT_MACHINE_R5=am62x_evm_r5_defconfig, build a new tiboot3-am62x-gp-evm.bin.

        b. Boot to U-Boot using SD card. Stop the autoboot.

        c. Send the following commands.

        

    mmc dev 0 0
setenv dfu_alt_info ${dfu_alt_info_emmc}
dfu 0 mmc 0

       d. Flash the tiboot3-am62x-gp-evm.bin, tispl.bin, u-boot.img and ext4 into emmc.

       e. Set back to emmc mode, no response at all.

    **I did the same thing on the other SD cards, I can't boot my board to U-Boot anymore, here's the error:

    Thanks,

    Koon Kee

  • 0 in reply to Lie Koon Kee
    TI__Guru**** 180506 points

    Hi Koon,

    I am routing your query to our U-Boot expert for comments.

  • 0 in reply to Bin Liu
    TI__Guru* 78090 points

    Hello Koon,
    Have you booted u-boot from any boot media on your customer board?
    If yes, will you share the full boot log starting from HW reset as an attachment?
    Best,
    -Hong

  • 0 in reply to Hong Guan64
    Prodigy 80 points

    Hi Hong,

    SD Card:

    SD card is booted using tisdk-default-image-am62xx-evm.wic.xz from /home/$USER/ti-processor-sdk-linux-am62xx-evm-09.00.00.03/filesystem/am62xx-evm. Only 1 card is usable, the same image when flashed into other SD cards doesn't work, I tried 3 SD cards in total.

    Lie Koon Kee said:

    **I did the same thing on the other SD cards, I can't boot my board to U-Boot anymore, here's the error:

    The same image only working in 1 SD card is another weird part in our findings, but it's not a big concern to us if you could help building tiboot3.bin for DFU boot since we want to flash our new processors using DFU, not SD cards. SD card only works as a temporary workaround for now.

    EMMC:

    EMMC is booting using tiboot3.bin, tispl.bin and u-boot.img from /home/$USER/ti-processor-sdk-linux-am62xx-evm-09.00.00.03/board-support/prebuilt-images/am62xx-evm. As mentioned in the thread, using the other tiboot3.bin would result in no response at all in serial console, including those that Bin guided me to build using the command make u-boot in tisdk 9.0 

    Thanks,

    Koon Kee

  • 0 in reply to Lie Koon Kee
    TI__Guru* 78090 points

    Hello Koon,
    I verified AM62x eMMC flashing with USB-DFU using Linux SDK 9.0 on AM62x-SK (HS-SE).
    I'm attaching logs for your reference:
    - am62x_9.0_emmc_flash_dfu_host.log: USB-DFU eMMC flashing host log
    - am62x_9.0_emmc_flash_dfu.log: USB-DFU eMMC flashing target log
    - am62x_9.0_emmc_boot.log: eMMC boot after flashing
    Best,
    -Hong

    Fullscreen am62x_9.0_emmc_flash_dfu_host.log Download 
    sitara@sitara-Latitude-E6410:~/test/SDK_debug/dfu/am62x_9.0/dfu$ sudo dfu-util -l
[sudo] password for sitara: 
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

Found DFU: [0451:6165] ver=0200, devnum=19, cfg=1, intf=0, alt=1, name="SocId", serial="01.00.00.00"
Found DFU: [0451:6165] ver=0200, devnum=19, cfg=1, intf=0, alt=0, name="bootloader", serial="01.00.00.00"
sitara@sitara-Latitude-E6410:~/test/SDK_debug/dfu/am62x_9.0/dfu$ sudo dfu-util -R -a bootloader -D tiboot3-am62x-hs-evm.bin
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

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%       309286 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
sitara@sitara-Latitude-E6410:~/test/SDK_debug/dfu/am62x_9.0/dfu$ sudo dfu-util -R -a tispl.bin -D tispl.bin
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

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 4096
Copying data from PC to DFU device
Download	[=========================] 100%      1138011 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
sitara@sitara-Latitude-E6410:~/test/SDK_debug/dfu/am62x_9.0/dfu$ sudo dfu-util -R -a u-boot.img -D u-boot.img
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

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 #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%       962779 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
sitara@sitara-Latitude-E6410:~/test/SDK_debug/dfu/am62x_9.0/dfu$ cd ../sdk_9.0
sitara@sitara-Latitude-E6410:~/test/SDK_debug/dfu/am62x_9.0/sdk_9.0$ sudo dfu-util -l
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

Found DFU: [0451:6165] ver=0223, devnum=22, cfg=1, intf=0, alt=6, name="sysfw.itb.raw", serial="0000000000000454"
Found DFU: [0451:6165] ver=0223, devnum=22, cfg=1, intf=0, alt=5, name="u-env.raw", serial="0000000000000454"
Found DFU: [0451:6165] ver=0223, devnum=22, cfg=1, intf=0, alt=4, name="u-boot.img.raw", serial="0000000000000454"
Found DFU: [0451:6165] ver=0223, devnum=22, cfg=1, intf=0, alt=3, name="tispl.bin.raw", serial="0000000000000454"
Found DFU: [0451:6165] ver=0223, devnum=22, cfg=1, intf=0, alt=2, name="tiboot3.bin.raw", serial="0000000000000454"
Found DFU: [0451:6165] ver=0223, devnum=22, cfg=1, intf=0, alt=1, name="rootfs", serial="0000000000000454"
Found DFU: [0451:6165] ver=0223, devnum=22, cfg=1, intf=0, alt=0, name="rawemmc", serial="0000000000000454"
sitara@sitara-Latitude-E6410:~/test/SDK_debug/dfu/am62x_9.0/sdk_9.0$ sudo dfu-util -a tiboot3.bin.raw -D tiboot3-am62x-hs-evm.bin
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

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 #2 ...
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%       293794 bytes
Download done.
state(7) = dfuMANIFEST, status(0) = No error condition is present
state(2) = dfuIDLE, status(0) = No error condition is present
Done!
sitara@sitara-Latitude-E6410:~/test/SDK_debug/dfu/am62x_9.0/sdk_9.0$ sudo dfu-util -a tispl.bin.raw -D tispl.bin
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

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 #3 ...
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%      1138011 bytes
Download done.
state(7) = dfuMANIFEST, status(0) = No error condition is present
state(2) = dfuIDLE, status(0) = No error condition is present
Done!
sitara@sitara-Latitude-E6410:~/test/SDK_debug/dfu/am62x_9.0/sdk_9.0$ sudo dfu-util -a u-boot.img.raw -D u-boot.img
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

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 #4 ...
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%       962779 bytes
Download done.
state(7) = dfuMANIFEST, status(0) = No error condition is present
state(2) = dfuIDLE, status(0) = No error condition is present
Done!
sitara@sitara-Latitude-E6410:~/test/SDK_debug/dfu/am62x_9.0/sdk_9.0$

    Fullscreen am62x_9.0_emmc_flash_dfu.log Download 
    U-Boot SPL 2023.04-00001-gf5b119738d15-dirty (Sep 25 2023 - 09:48:04 -0500)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
SPL initial stack usage: 13376 bytes
Trying to boot from DFU
########################################################DOWNLOAD ... OK
Ctrl+C to exit ...
alloc space exhausted
Could not get FIT buffer of 1138012 bytes
	check CONFIG_SYS_SPL_MALLOC_SIZE
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Loading Environment from nowhere... OK
init_env from device 10 not supported!
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE:  BL31: Built : 00:42:57, Jan 13 2023

U-Boot SPL 2023.04-g24098ea90d (Jul 06 2023 - 12:59:40 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
SPL initial stack usage: 1856 bytes
Error (-2): cannot determine file size
Trying to boot from DFU
################################################DOWNLOAD ... OK
Ctrl+C to exit ...
Authentication passed
Authentication passed


U-Boot 2023.04-g24098ea90d (Jul 06 2023 - 12:59:40 +0000)

SoC:   AM62X SR1.0 HS-SE
Model: Texas Instruments AM625 SK
EEPROM not available at 80, trying to read at 81
Board: AM62B-SKEVM rev A
DRAM:  2 GiB
Core:  71 devices, 31 uclasses, devicetree: separate
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  2  1  0 
=> setenv dfu_alt_info ${dfu_alt_info_emmc}
=> dfu 0 mmc 0
generic_phy_get_bulk : no phys property
###############DOWNLOAD ... OK
Ctrl+C to exit ...
########################################################DOWNLOAD ... OK
Ctrl+C to exit ...
################################################DOWNLOAD ... OK
Ctrl+C to exit ...

    Fullscreen am62x_9.0_emmc_boot.log Download 
    U-Boot SPL 2023.04-g24098ea90d (Jul 06 2023 - 12:59:40 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
SPL initial stack usage: 13376 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE:  BL31: Built : 00:42:57, Jan 13 2023

U-Boot SPL 2023.04-g24098ea90d (Jul 06 2023 - 12:59:40 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
SPL initial stack usage: 1856 bytes
Error (-2): cannot determine file size
Trying to boot from MMC1
Authentication passed
Authentication passed


U-Boot 2023.04-g24098ea90d (Jul 06 2023 - 12:59:40 +0000)

SoC:   AM62X SR1.0 HS-SE
Model: Texas Instruments AM625 SK
EEPROM not available at 80, trying to read at 81
Board: AM62B-SKEVM rev A
DRAM:  2 GiB
Core:  71 devices, 31 uclasses, devicetree: separate
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  2  0 
=> md.l 0x43000030 1
43000030: 000000cb                             ....
=>

  • 0 in reply to Hong Guan64
    Prodigy 80 points

    Hi Hong,

    Could you please attach the tiboot3-am62x-hs-evm.bin you used in sudo dfu-util -R -a bootloader -D tiboot3-am62x-hs-evm.bin so that I can test it out with my new AM6232 processor?

    As mentioned previously, the tiboot3.bin that I built using make u-boot after setting UBOOT_MACHINE_R5=am62x_evm_r5_usbdfu_defconfig (following Bin's guide) worked on AM62-SK board and custom boards with AM6234 processor, but it does not work on my new custom board with AM6232 processor.

    Thanks,

    Koon Kee

  • 0 in reply to Lie Koon Kee
    TI__Guru* 78090 points
    Lie Koon Kee said:
    Could you please attach the tiboot3-am62x-hs-evm.bin you used in sudo dfu-util -R -a bootloader -D tiboot3-am62x-hs-evm.bin

    I'm attaching the binary used in my test from my last reply

    Hong Guan64 said:
    I verified AM62x eMMC flashing with USB-DFU using Linux SDK 9.0 on AM62x-SK (HS-SE).

    Best,
    -Hong

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/tiboot3_2D00_am62x_2D00_hs_2D00_evm.bin