AM6411: Booting AM6411

Part Number: AM6411
Other Parts Discussed in Thread: SK-AM64B, , SYSCONFIG, AM6442, SK-AM62B

Tool/software:

I've a custom AM6411 board derived from SK-AM64B.  I've got a few questions.

I've got the debian trixie 11.00.09.04 (Apr 4, 2025) image burned and am trying to boot.  Not working, you can see the log below.  I'm not terribly surprised because...

  • I presume I need to build a new dtb file to boot
  • Do I also need to re-build U-boot stuff too?

Can you help me with a high level overview of what needs to be done?

I was hoping to generate the dts file using the SysConfig tool, but I'm a bit confused about this.  Seems there are multiple ways to run the SysConfig tool.

(1) I don't seem to be able to configure the DDR memory here.
https://dev.ti.com/sysconfig

Note in this first method to run the SysConfig, I do not select a software product.  I've used this in the past to configure different hardware with AM6442 (with AM6442 selected instead).

But it seems I'm unable to get the ddr to actually configure?  Is this something I need to worry about?  I imagine I need to specify the size?

However, I see I can run this tool in a different fashion, with Software Product selected for DDR.

Now I get stuff for ddr config... how am I supposed to use this?  I see you link to the README: https://dev.ti.com/tirex/content/Processor_DDR_Config_0.10.32.0000/docs/README.html

However I think my memory may be the same from the AM6442 --> AM6411, so ideally I don't need to bother with this, but I'm confused a bit how running the SysConfig in these different methods should be used.

(2) Is there a way I'm supposed to be able to disable the other cores since I'm using AM6411?

  • Like SDK hit has k3-am642-sk.dts which includes k3-am642.dtsi
    • Do I need to create a new k3-am641.dtsi that doesn't include the second core?
    • And make myself a k3-am641-myboard.dts?
    • Anything with U-boot?

For the record, here's the log of what I've got now:

U-Boot SPL 2025.01-00406-gcd91d7360181 (Mar 25 2025 - 16:14:37 +0000)
Resetting on cold boot to workaround ErrataID:i2331
Please resend tiboot3.bin in case of UART/DFU boot
resetting ...

U-Boot SPL 2025.01-00406-gcd91d7360181 (Mar 25 2025 - 16:14:37 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000b '11.0.7--v11.00.07 (Fancy Rat)')
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -121
SPL initial stack usage: 13392 bytes

U-Boot SPL 2025.01-00406-gcd91d7360181 (Mar 25 2025 - 16:14:37 +0000)
Resetting on cold boot to workaround ErrataID:i2331
Please resend tiboot3.bin in case of UART/DFU boot
resetting ...

U-Boot SPL 2025.01-00406-gcd91d7360181 (Mar 25 2025 - 16:14:37 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000b '11.0.7--v11.00.07 (Fancy Rat)')
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -121
SPL initial stack usage: 13392 bytes

  • Hi Timothy,

    First of all, I modified your post to put the console log into a code block so that we have line numbers for communication.

    In the console log, line 12 repeats line 1. Did you power cycle or warm reset the board causing line 12 messages? or is it automatically printed without you touching the board?

    I was hoping to generate the dts file using the SysConfig tool, but I'm a bit confused about this.  Seems there are multiple ways to run the SysConfig tool.

    Let's put the SysConfig tool aside for now. We will come back on it later if necessary.

    However I think my memory may be the same from the AM6442 --> AM6411,

    Do you mean you use the exact same DDR memory (type and size) as that the SK-AM62B EVM?

    (2) Is there a way I'm supposed to be able to disable the other cores since I'm using AM6411?

    It is only relevant in kernel, the number of A53 cores doesn't matter in U-Boot. Let's first ensure you can boot into U-Boot command line prompt first.

  • Hi Bin, 

    I'm working with Timothy on this project. I can confirm that I power cycled the device after line 10 was printed, which is why the console log repeats. 

  • Hi Connor,

    Thanks for confirming it.

    I assume your board doesn't have EEPROM? Please apply the two U-Boot patches I posted in the link below, to see if it can make U-Boot print more message on your board.

     AM6412: Is it possible to skip read eeprom for board id? 

  • Hi Bin,

    So I sort of made progress.  I was able to recompile U-Boot, but I had to cheat and take the bl31.bin and bl32.bin from the prebuilt directory because I couldn't get optee or trusted-firmware built --> is this ok?  I also show my other updates to attempt to match the two updates in the other post.  Have yet to try this.

    So I've found CONFIG_SPL_OF_LIST, but no CONFIG_OF_LIST.  Made the update to:

    ./ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/configs/am64x_evm_r5_defconfig
    -CONFIG_SPL_OF_LIST="k3-am642-r5-evm k3-am642-r5-sk"
    +CONFIG_SPL_OF_LIST="k3-am642-r5-sk"


    Here's the other update...

    # This Kconfig path seen didn't seem right as seemed to be from other post, however...
    ./ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/board/ti/am64x/Kconfig
    
    # This Kconfig matches what you gave...
    ./ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/arch/arm/mach-k3/am64x/Kconfig
    Now I've got...
    ...
    config TARGET_AM642_R5_EVM
    	bool "TI K3 based AM642 EVM running on R5"
    	select CPU_V7R
    	select SYS_THUMB_BUILD
    	select K3_LOAD_SYSFW
    	select RAM
    	select SPL_RAM
    	select K3_DDRSS
    	select BINMAN
    	imply SYS_K3_SPL_ATF
    #	imply TI_I2C_BOARD_DETECT
    

    Here you can see where I took bl31.bin and bl32.bin and stuck into "output" directories so U-Boot would build.  I ended up taking them from the prebuilt-images directory and was able to fully compile.  I think that's ok to use these prebuilt files for the purposes here?

    user@box:~/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support$ find . | grep bl31.bin$
    ./prebuilt-images/am64xx-evm/bl31.bin
    ./trusted-firmware-a-2.12+git/build/k3/lite/release/bl31.bin
    user@box:~/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support$ find . | grep bl32.bin$
    ./optee-os-4.5.0+git/out/arm-plat-k3/core/bl32.bin
    ./prebuilt-images/am64xx-evm/bl32.bin
    

    I would like to understand why I couldn't build optee and trusted-formware.  I had an issue with libgcc.a not being found.

    * I was able to eliminate this error by running linux-devkit/environment-setup-aarch64-oe-linux
       * But then had to unset ARCH which was set to arm64, and there was no arm64 directory.

    user@box:~/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/optee-os-4.5.0+git$ make CROSS_COMPILE="$CROSS_COMPILE_32" CROSS_COMPILE64="$CROSS_COMPILE_64" PLATFORM=k3-am64x CF
    ...
      CC      out/arm-plat-k3/ldelf-lib/libutils/ext/qsort_helpers.o
      CC      out/arm-plat-k3/ldelf-lib/libutils/ext/array.o
      CC      out/arm-plat-k3/ldelf-lib/libutils/ext/base64.o
      AS      out/arm-plat-k3/ldelf-lib/libutils/ext/arch/arm/atomic_a64.o
      CC      out/arm-plat-k3/ldelf-lib/libutils/ext/arch/arm/auxval.o
      AR      out/arm-plat-k3/ldelf-lib/libutils/libutils.a
      CPP     out/arm-plat-k3/ldelf/ldelf.lds
      LD      out/arm-plat-k3/ldelf/ldelf.elf
    ~/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/aarch64-oe-linux/aarch64-oe-linux-ld.bfd: cannot find libgcc.a: No such file or directory
    make: *** [ldelf/link.mk:60: out/arm-plat-k3/ldelf/ldelf.elf] Error 1
    

    I also tried ti-processor-sdk-linux-rt-am64xx-evm-11.01.05.03, but then I had issues with the python cryptography library missing?

    The output of this command shows the same files in both 11.00... and 11.01..; I guess this is not complete? user@box:~$ find . | grep crypt | grep python

    /licenses/native/python3-cryptography-native
    /licenses/native/python3-cryptography-native/generic_BSD-3-Clause
    /licenses/native/python3-cryptography-native/recipeinfo
    /licenses/native/python3-cryptography-native/LICENSE.BSD
    /licenses/native/python3-cryptography-native/LICENSE
    /licenses/native/python3-cryptography-native/LICENSE.APACHE
    /licenses/native/python3-cryptography-native/generic_Apache-2.0
    /licenses/native/python3-pycryptodome-native
    /licenses/native/python3-pycryptodome-native/recipeinfo
    /licenses/native/python3-pycryptodome-native/generic_BSD-2-Clause
    /licenses/native/python3-pycryptodome-native/LICENSE.rst
    /licenses/native/python3-pycryptodome-native/generic_PD
    /linux-devkit/sysroots/aarch64-oe-linux/usr/lib/python3.12/crypt.py
    /linux-devkit/sysroots/aarch64-oe-linux/usr/lib/python3.12/lib-dynload/_crypt.cpython-312-aarch64-linux-gnu.so
    /linux-devkit/sysroots/aarch64-oe-linux/usr/lib/python3.12/__pycache__/crypt.cpython-312.pyc
    /linux-devkit/sysroots/aarch64-oe-linux/var/lib/opkg/info/python3-crypt.control
    /linux-devkit/sysroots/aarch64-oe-linux/var/lib/opkg/info/python3-crypt.list
    /linux-devkit/sysroots/x86_64-arago-linux/usr/lib/python3.12/crypt.py
    /linux-devkit/sysroots/x86_64-arago-linux/usr/lib/python3.12/lib-dynload/_crypt.cpython-312-x86_64-linux-gnu.so
    /linux-devkit/sysroots/x86_64-arago-linux/usr/lib/python3.12/__pycache__/crypt.cpython-312.pyc
    /linux-devkit/sysroots/x86_64-arago-linux/var/lib/opkg/info/nativesdk-python3-crypt.list
    /linux-devkit/sysroots/x86_64-arago-linux/var/lib/opkg/info/nativesdk-python3-crypt.control
    /k3r5-devkit/sysroots/x86_64-arago-linux/usr/lib/python3.12/crypt.py
    /k3r5-devkit/sysroots/x86_64-arago-linux/usr/lib/python3.12/lib-dynload/_crypt.cpython-312-x86_64-linux-gnu.so
    /k3r5-devkit/sysroots/x86_64-arago-linux/usr/lib/python3.12/__pycache__/crypt.cpython-312.pyc
    /k3r5-devkit/sysroots/x86_64-arago-linux/var/lib/opkg/info/nativesdk-python3-crypt.list
    /k3r5-devkit/sysroots/x86_64-arago-linux/var/lib/opkg/info/nativesdk-python3-crypt.control
    

    My understanding is to stick these files on the first partition of sdcard in and see how things go?

    user@box:~/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git$ find . -printf "%s %TY-%Tm-%Td %TH:%TM %p\n" | grep tiboot3.bin$
    33 2025-10-02 16:29 ./out/r5/tiboot3.bin
    user@box:~/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git$ find . -printf "%s %TY-%Tm-%Td %TH:%TM %p\n" | grep tispl.bin$
    943711 2025-10-02 16:42 ./out/a53/tispl.bin
    user@box:~/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git$ find . -printf "%s %TY-%Tm-%Td %TH:%TM %p\n" | grep u-boot.img$
    645472 2025-10-02 16:29 ./out/r5/u-boot.img
    1443139 2025-10-02 16:42 ./out/a53/u-boot.img
    

    I mounted the Debian image and checked the target files:

    timothy@box:~/Downloads$ ls -al
    total 3322181
    drwxr-xr-x  4 timothy timothy       4096 Oct  3 00:58 .
    drwxr-x--- 20 timothy timothy       4096 Oct  2 17:32 ..
    drwxr-xr-x  2 root    root           512 Dec 31  1969 m1
    drwxr-xr-x 18 root    root          4096 Apr  3  2025 m2
    -rwxr-xr-x  1 timothy timothy 2077415982 Oct  2 16:49 ti-processor-sdk-linux-rt-am64xx-evm-11.01.05.03-Linux-x86-Install.bin
    -rw-rw-r--  1 timothy timothy 5368709120 Oct  3 00:59 tisdk-debian-trixie-rt-am64xx-evm-11.00.09.04.wic
    timothy@box:~/Downloads$ ls -al m1
    total 2848
    drwxr-xr-x 2 root    root        512 Dec 31  1969 .
    drwxr-xr-x 4 timothy timothy    4096 Oct  3 00:58 ..
    -rwxr-xr-x 1 root    root     528270 Apr  3  2025 tiboot3.bin
    -rwxr-xr-x 1 root    root     939599 Apr  3  2025 tispl.bin
    -rwxr-xr-x 1 root    root    1442643 Apr  3  2025 u-boot.img
    timothy@box:~/Downloads$ 

    Seems the tiboot3.bin filesize above is just the link, here are the files in proper:

    timothy@box:~/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/out/r5$ ls -al tiboot3*
    -rw-rw-r-- 1 timothy timothy 501145 Oct  2 16:29 tiboot3-am64x-gp-evm.bin
    -rw-rw-r-- 1 timothy timothy    279 Oct  2 16:29 tiboot3-am64x-gp-evm.bin.map
    -rw-rw-r-- 1 timothy timothy 503734 Oct  2 16:29 tiboot3-am64x_sr2-hs-evm.bin
    -rw-rw-r-- 1 timothy timothy    328 Oct  2 16:29 tiboot3-am64x_sr2-hs-evm.bin.map
    -rw-rw-r-- 1 timothy timothy 503734 Oct  2 16:29 tiboot3-am64x_sr2-hs-fs-evm.bin
    -rw-rw-r-- 1 timothy timothy    331 Oct  2 16:29 tiboot3-am64x_sr2-hs-fs-evm.bin.map
    lrwxrwxrwx 1 timothy timothy     33 Oct  2 16:29 tiboot3.bin -> ./tiboot3-am64x_sr2-hs-fs-evm.bin
    -rw-rw-r-- 1 timothy timothy 506242 Oct  2 16:29 tiboot3-capsule.bin

    I am concerned if I've getting the write files, there are several as illustrated in the linking of tiboot3.bin above.  Also, do I need to boot fit images?

    73,
    Timothy

  • Hi Timothy,

    I was able to recompile U-Boot, but I had to cheat and take the bl31.bin and bl32.bin from the prebuilt directory because I couldn't get optee or trusted-firmware built --> is this ok?

    Yes, the SDK prebuilt bl31.bin and bl32.bin are okay to use for re-compiling U-Boot. You don't need to rebuild them unless you modified their source code.

    BTY, I am not sure how you rebuilt the SDK U-Boot, the simplest way is to use command 'make u-boot' at the SDK top level directory, and output binaries are under <SDK>/board-support/u-boot-build/ directory.

    So I've found CONFIG_SPL_OF_LIST, but no CONFIG_OF_LIST.  Made the update to:

    CONFIG_OF_LIST is defined in configs/am64x_evm_a53_defconfig. You need to modify it there.

    > # This Kconfig path seen didn't seem right as seemed to be from other post, however...
    > ./ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/board/ti/am64x/Kconfig

    > # This Kconfig matches what you gave...
    > ./ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/arch/arm/mach-k3/am64x/Kconfig

    Correct, the EVM board Kconfig options have been re-structured in newer U-Boot versions.

    > Now I've got...
    > ...
    > config TARGET_AM642_R5_EVM
    >     bool "TI K3 based AM642 EVM running on R5"
    >     ...
    >     #    imply TI_I2C_BOARD_DETECT

    You also need to remove "imply TI_I2C_BOARD_DETECT" in the "config TARGET_AM642_A53_EVM" entry too.

    I would like to understand why I couldn't build optee and trusted-formware.  I had an issue with libgcc.a not being found.

    I believe this is a bug in the trusted-firmware code, which fails to build in the SDK environment. But you can ignore this error and directly use the prebuilt binaries in the SDK.

    My understanding is to stick these files on the first partition of sdcard in and see how things go?

    Yes, update the 3 U-Boot binaries in the SDcard boot partition.

    Seems the tiboot3.bin filesize above is just the link, here are the files in proper:

    > tiboot3.bin -> ./tiboot3-am64x_sr2-hs-fs-evm.bin

    Yes, this is the tiboot3.bin binary for SK-AM62B.

  • Thanks, I made those updates and tried to build from top level, received this error:

    user@box:~/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04$ make clean
    
    user@box:~/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04$ make u-boot
    ##snip##
      CC      spl/drivers/usb/host/xhci-ring.o
      AR      spl/drivers/usb/host/built-in.o
      AR      spl/drivers/built-in.o
      LD      spl/u-boot-spl
      OBJCOPY spl/u-boot-spl-nodtb.bin
      SYM     spl/u-boot-spl.sym
      CAT     spl/u-boot-spl-dtb.bin
      COPY    spl/u-boot-spl.bin
      BINMAN  .binman_stamp
    Image 'ti-spl' is missing external blobs and is non-functional: blob-ext
    
    /binman/ti-spl/fit/images/fdt-0/blob-ext (spl/dts/ti/k3-am642-evm.dtb):
       Missing blob
    
    Image 'ti-spl' has faked external blobs and is non-functional: k3-am642-evm.dtb
    
    binman: Filename 'spl/dts/ti/k3-am642-evm.dtb' not found in input path (.,/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git,/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/board/ti/am64x,dts/upstream/src/arm64,/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/prebuilt-images/am64xx-evm) (cwd='/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/u-boot-build/a53')
    make[2]: *** [/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/Makefile:1135: .binman_stamp] Error 1
    make[2]: Leaving directory '/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/u-boot-build/a53'
    make[1]: *** [Makefile:177: sub-make] Error 2
    make[1]: Leaving directory '/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git'
    make: *** [makerules/Makefile_u-boot:11: u-boot-a53] Error 2
    user@box:~/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04$ 
    

    Before I was following instructions at link below to build U-Boot:

    https://software-dl.ti.com/processor-sdk-linux-rt/esd/AM64X/11_00_09_04/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html#build-u-boot

    I'm getting a similar error to above doing this now:

    user@box:~/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git$ make ARCH=arm CROSS_COMPILE="$CROSS_COMPILE_64" CC="$CC_64" BL31=$TFA_DIR/build/k3/lite/release/bl31.bin TEE=$OPTEE_DIR/out/arm-plat-k3/core/bl32.bin O=$UBOOT_DIR/out/a53 BINMAN_INDIRS=$TI_LINUX_FW_DIR
    ##SNIP##
      CC      spl/net/net-common.o
      AR      spl/net/built-in.o
      LDS     spl/u-boot-spl.lds
      LD      spl/u-boot-spl
      OBJCOPY spl/u-boot-spl-nodtb.bin
      FDTGREP spl/dts/ti/k3-am642-sk.dtb
      MKIMAGE spl/u-boot-spl.multidtb.fit
      CAT     spl/u-boot-spl-dtb.bin
      COPY    spl/u-boot-spl.bin
      SYM     spl/u-boot-spl.sym
      MKIMAGE u-boot.img
      COPY    u-boot.dtb
      MKIMAGE u-boot-dtb.img
      BINMAN  .binman_stamp
    Image 'ti-spl' is missing external blobs and is non-functional: blob-ext
    
    /binman/ti-spl/fit/images/fdt-0/blob-ext (spl/dts/ti/k3-am642-evm.dtb):
       Missing blob
    
    Image 'ti-spl' has faked external blobs and is non-functional: k3-am642-evm.dtb
    
    binman: Filename 'spl/dts/ti/k3-am642-evm.dtb' not found in input path (.,/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git,/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/board/ti/am64x,dts/upstream/src/arm64,/home/timothy/workgit/ti-linux-firmware) (cwd='/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/out/a53')
    make[1]: *** [/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/Makefile:1135: .binman_stamp] Error 1
    make[1]: Leaving directory '/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/out/a53'
    make: *** [Makefile:177: sub-make] Error 2
    user@box:~/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git$
    

    73,
    Timothy

  • Ok,

    I renamed the sdk install dir, re-installed sdk.  Sucessfully built using: make u-boot from top level.

    I applied the changes (I used # to comment out, I presume that's right):

    /home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/arch/arm/mach-k3/am64x/Kconfig
    two removals of "imply TI_I2C_BOARD_DETECT"
    
    /home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/board/ti/common/Kconfig
    two removals of "depends on TI_I2C_BOARD_DETECT"
    
    /home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/configs/am64x_evm_a53_defconfig
    #CONFIG_OF_LIST="ti/k3-am642-evm ti/k3-am642-sk"
    CONFIG_OF_LIST="ti/k3-am642-sk"
    
    /home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/configs/am64x_evm_r5_defconfig
    #CONFIG_SPL_OF_LIST="k3-am642-r5-evm k3-am642-r5-sk"
    CONFIG_SPL_OF_LIST="k3-am642-r5-sk"
    
    

    I ran make u-boot (didn't do a clean)... got same error...

      CC      spl/drivers/usb/host/xhci-ring.o
      AR      spl/drivers/usb/host/built-in.o
      AR      spl/drivers/built-in.o
      LD      spl/u-boot-spl
      OBJCOPY spl/u-boot-spl-nodtb.bin
      SYM     spl/u-boot-spl.sym
      CAT     spl/u-boot-spl-dtb.bin
      COPY    spl/u-boot-spl.bin
      BINMAN  .binman_stamp
    Image 'ti-spl' is missing external blobs and is non-functional: blob-ext
    
    /binman/ti-spl/fit/images/fdt-0/blob-ext (spl/dts/ti/k3-am642-evm.dtb):
       Missing blob
    
    Image 'ti-spl' has faked external blobs and is non-functional: k3-am642-evm.dtb
    
    binman: Filename 'spl/dts/ti/k3-am642-evm.dtb' not found in input path (.,/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git,/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/board/ti/am64x,dts/upstream/src/arm64,/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/prebuilt-images/am64xx-evm) (cwd='/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/u-boot-build/a53')
    make[2]: *** [/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/Makefile:1135: .binman_stamp] Error 1
    make[2]: Leaving directory '/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/u-boot-build/a53'
    make[1]: *** [Makefile:177: sub-make] Error 2
    make[1]: Leaving directory '/home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git'
    make: *** [makerules/Makefile_u-boot:11: u-boot-a53] Error 2
    timothy@box:~/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04$ 

    Also tried again with a make clean first, same issue.

    ----

    I will try messing around a bit.  For instance, if I'm removing other evm stuff, I wonder if the changes below should be made.
    /home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/configs/am64x_evm_a53_defconfig
    CONFIG_DEFAULT_DEVICE_TREE="ti/k3-am642-evm"    -?-> "ti/k3-am642-sk"
    CONFIG_TARGET_AM642_A53_EVM=y   -?-> n


    /home/timothy/ti-processor-sdk-linux-rt-am64xx-evm-11.00.09.04/board-support/ti-u-boot-2025.01+git/configs/am64x_evm_r5_defconfig
    CONFIG_DEFAULT_DEVICE_TREE="k3-am642-r5-evm"  -?-> "k3-am642-r5-sk"
    CONFIG_TARGET_AM642_R5_EVM=y    -?-> n

    73,
    Timothy

  • Didn't have success with the above items.  What I ended up doing only applying the 2nd fix from the other email... to remove the 

    • imply TI_I2C_BOARD_DETECT
    • depends on TI_I2C_BOARD_DETECT

    We'll try that.