• State
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 29 replies
  • Subscribers 98 subscribers
  • Views 871 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.

TDA4VM: Encountering inconsistent issues during dfu flashing on different versions of TDA4VM's SDK

Jiahui Gao
Genius 10895 points

Part Number: TDA4VM
Other Parts Discussed in Thread: DRA829,

Hi team,

1. I encountered an issue where DFU flashing is not functioning when using different versions of the PROCESSOR-SDK-LINUX-J721E Linux SDK for DRA829 & TDA4VM Jacinto™ Processors. The problematic version is: 10.01.00.04 (2024-12-18). The version without the issue is: 09.02.00.05 (2024-4-8)

2. The issue manifests as follows: when I use the boot-adas-j721e-evm.tar.gz file from version 10.01.00.04 (2024-12-18)
During the DFU firmware upgrade process, the device encountered an issue where it could not enter DFU mode. The host completed the operation on Linux
sudo dfu-util -R -a bootloader -D tiboot3.bin
sudo dfu-util -R -a sysfw.itb -D sysfw.itb
The serial UART terminal displays the following information:

However, in version 09.02.00.05 (2024-4-8), executing commands in the Linux terminal...
sudo dfu-util -R -a bootloader -D tiboot3.bin
sudo dfu-util -R -a sysfw.itb -D sysfw.itb
The serial terminal displays different types of print information:

It can be clearly seen that version 09.02.00.05 (2024-4-8) can enter DFU mode to start, but version 10.01.00.04 (2024-12-18) does not have printing information for Trying to boot from DFU. But their operations are consistent.
Question:
I observed that the SYSFW ABI versions of 09.02.00.05 (2024-4-8) and 10.01.00.04 (2024-12-18) are different.
I would like to know the difference between SYSFW ABI: 4.0 and SYSFW ABI: 3.1. Is it due to the error caused by SYSFW ABI: 4.0 version.
 
Note:
My other steps are the same, all follow the manual operation, the only difference is the SDK version. UART printing information
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -121
It shouldn't be the cause of the problem, as both versions have this printing information.

  • 0
    Intellectual 260 points

    Hello team, this issue is extremely important to me. I hope to adapt it to version 10.01.00.04 (2024-12-18)

  • 0 in reply to ? ??
    TI__Mastermind 19040 points

    Hi Jiahui,

    I tested the same on my end  on TI J721E EVM with the boot images present in the <10.01 SDK dir>/prebuilt-images folder and it works fine.

    Host side logs:

    ~/ti-processor-sdk-linux-adas-j721e-evm-10_01_00_04/board-support/prebuilt-images$ 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:6163] ver=0200, devnum=37, cfg=1, intf=0, path="1-11.1.3", alt=1, name="SocId", serial="01.00.00.00"
Found DFU: [0451:6163] ver=0200, devnum=37, cfg=1, intf=0, path="1-11.1.3", alt=0, name="bootloader", serial="01.00.00.00"

~/ti-processor-sdk-linux-adas-j721e-evm-10_01_00_04/board-support/prebuilt-images$ 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: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%       282001 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

$ 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:6163] ver=0224, devnum=41, cfg=1, intf=0, path="1-11.1.3", alt=0, name="sysfw.itb", serial="UNKNOWN"

~/ti-processor-sdk-linux-adas-j721e-evm-10_01_00_04/board-support/prebuilt-images$ sudo dfu-util -R -a bootloader -D 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 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!!!
dfu-util: No DFU capable USB device available

~/ti-processor-sdk-linux-adas-j721e-evm-10_01_00_04/board-support/prebuilt-images$ sudo dfu-util -R -a sysfw.itb -D 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 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: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%       268978 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

    Target side Logs:

    Regards

    Gokul Praveen

  • 0 in reply to Gokul Praveen
    Intellectual 260 points
    Hello, thank you for your support. Since there have been no changes to my custom hardware device, the only difference lies in the versions of the SDK. The version 09.02.00.05 (released on April 8, 2024) supports normal DFU (Device Firmware Update) flashing, while the version 10.01.00.04 (released on December 18, 2024) does not allow normal DFU flashing.
    Do you have any information regarding the updates made to the DFU component between these two versions? Could you also provide some suggestions to help me troubleshoot this issue?
  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    Secondly, I have a J721EXSOMG01EVM board in hand and plan to use it for experiments. Do you have any relevant documents on how to perform DFU flashing with this board?

  • 0 in reply to ? ??
    TI__Mastermind 19040 points

    Hi ? ??,

    You can follow section 5.1.3 dfu-util from the below document for dfu flashing with this board.7658.TDA4_FLASHING_TECHNIQUES.pdf

    Regards

    Gokul Praveen

  • 0 in reply to Gokul Praveen
    Intellectual 260 points
    I confirm that my steps are consistent with the document you sent and there are no errors. This is because I can use DFU (Device Firmware Update) normally on the version 09.02.00.05 (released on April 8, 2024), but when using the exact same steps on the version 10.01.00.04 (released on December 18, 2024), the firmware flashing cannot be performed properly.
    1. I would like to ask: From version 09.02.00.05 to 10.01.00.04, have there been any changes to the hardware and software related to DFU?
    2. Could you provide the DFU operation manual for the J721EXSOMG01EVM board?
  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    Hello, has there been any progress on the current issue

  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    Hello, has there been any progress on the current issue

  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    Hello, has there been any progress on the current issue

  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    Hello, has there been any progress? Do you need me to post a new one? This question is very important to me. Thank you for your support.

  • 0 in reply to ? ??
    TI__Mastermind 19040 points

    Hi ? ??

    Gokul Praveen said:
    I tested the same on my end  on TI J721E EVM with the boot images present in the <10.01 SDK dir>/prebuilt-images folder and it works fine.

    The DFU version 10.01.00.04 works fine on our board. I am not sure on why this is failing on your custom board.

  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    I have a few key questions：

    1.I would like to know the difference between SYSFW ABI: 4.0 and SYSFW ABI: 3.1. Is it due to the error caused by SYSFW ABI: 4.0 version. 

    2.I would like to ask: From version 09.02.00.05 to 10.01.00.04, have there been any changes to the hardware and software related to DFU?

    3.Could you provide the DFU operation manual for the J721EXSOMG01EVM board?

  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    Since there have been no changes to my custom hardware, the only variable that has changed is the SDK version. Moreover, my custom hardware supports DFU (Device Firmware Update) for version 09.02.00.05 (released on April 8, 2024), so I am more focused on the changes made to the SDK.
    Additionally, I have the J721EXSOMG01EVM board on hand, but I do not know how to use it for DFU operations. Therefore, could you please provide an operation manual so that I can attempt to perform DFU on the J721EXSOMG01EVM board using version 10.01.00.04?

  • 0 in reply to ? ??
    TI__Mastermind 19040 points

    Hi ? ??,

    ? ?? said:
    Additionally, I have the J721EXSOMG01EVM board on hand, but I do not know how to use it for DFU operations. Therefore, could you please provide an operation manual so that I can attempt to perform DFU on the J721EXSOMG01EVM board using version 10.01.00.04?

    The below link has the documentation for DFU boot mode on 10.01 SDK

    https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-jacinto7/10_01_00_04/exports/docs/linux/Foundational_Components/U-Boot/UG-DFU.html?highlight=dfu

    Regards

    Gokul Praveen

  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    Is my J721EXSOMG01EVM device not compatible with DFU? According to the following introduction：

    Do you have an answer to this question now?

    2.I would like to ask: From version 09.02.00.05 to 10.01.00.04, have there been any changes to the hardware and software related to DFU?

  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    Hello, has there been any progress on the current issue

  • 0 in reply to ? ??
    TI__Mastermind 19040 points

    Hi ? ??

    Can you check the revision of the J721EXSOMG01EVM?

    Regards

    Gokul Praveen

  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    I don't know the specific version number you need. There is only this serial number on my physical board.

    Could you please tell me how to operate it to perform DFU?

    Additionally, can you reply to me directly regarding this issue?

    2.I would like to ask: From version 09.02.00.05 to 10.01.00.04, have there been any changes to the hardware and software related to DFU?

  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    Hello, has there been any progress on the current issue

  • 0 in reply to ? ??
    TI__Mastermind 19040 points

    Hi ? ??,

    ? ?? said:
    2.I would like to ask: From version 09.02.00.05 to 10.01.00.04, have there been any changes to the hardware and software related to DFU?

    The hardware has not changed but there has been software changes in UBOOT USB driver. Since, UBOOT is an open source software , it is impractical to mention the changes as there are a lot of changes that has gone in from people all over the world.

    ? ?? said:
    Could you please tell me how to operate it to perform DFU?
    • Can you share the U-BOOT boot logs while trying to boot using DFU on 09.02.00.05 SDK? It will help us get the revision number, as the images you have shared does not have the revision number.
    • Have you made any code changes on top of the default 10.01 SDK ?
    • Can you try flashing the tiboot3.bin,tispl.bin and u-boot.img present in the <10.01 SDK_DIR>/board-support/prebuilt-images directory using DFU and share the logs as well.

    Note : Please test all of these on J721EXSOMG01EVM

    Regards

    Gokul Praveen

  • 0 in reply to ? ??
    Intellectual 260 points

    Hello, are you still assisting with this issue? Could you please respond to the question I raised earlier?

  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    Hello Gokul Praveen,

    I think I've identified the root cause of the issue—it's because my custom circuit board lacks the EEPROM chip (designator: U16) present on the J721EXSOMG01EVM board. After I subsequently soldered this chip onto my custom board, the error message disappeared and DFU now works normally。

    I have a few questions and would appreciate your help with them:
    1. What is the function of this EEPROM chip (designator: U16)?
    2. I noticed there are also error messages related to the EEPROM in version 09.02.00.05 (released on April 8, 2024) from forum posts—so why has it become mandatory in version 10.01.00.04 (released on December 18, 2024)?
    3. Is there any way for me to operate without this EEPROM chip (designator: U16) in version 10.01.00.04 (released on December 18, 2024)?
  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    Just to interject with an update: I just attempted the full DFU procedure, and an error still occurred.

    Host side logs:

    ljy@ubuntu:~/test/board-support/prebuilt-images$ 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:6163] ver=0200, devnum=23, cfg=1, intf=0, path="1-1", alt=1, name="SocId", serial="01.00.00.00"
Found DFU: [0451:6163] ver=0200, devnum=23, cfg=1, intf=0, path="1-1", alt=0, name="bootloader", serial="01.00.00.00"
ljy@ubuntu:~/test/board-support/prebuilt-images$ 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: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%       282001 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
ljy@ubuntu:~/test/board-support/prebuilt-images$ sudo dfu-util -R -a sysfw.itb -D 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 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: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%       268978 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
ljy@ubuntu:~/test/board-support/prebuilt-images$ 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:6163] ver=0224, devnum=25, cfg=1, intf=0, path="1-1", alt=1, name="u-boot.img", serial="UNKNOWN"
Found DFU: [0451:6163] ver=0224, devnum=25, cfg=1, intf=0, path="1-1", alt=0, name="tispl.bin", serial="UNKNOWN"
ljy@ubuntu:~/test/board-support/prebuilt-images$ sudo dfu-util -R -a tispl.bin -D tispl.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: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%      1090079 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
ljy@ubuntu:~/test/board-support/prebuilt-images$ 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/

ljy@ubuntu:~/test/board-support/prebuilt-images$ sudo dfu-util -R -a u-boot.img -D u-boot.img
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!!!
dfu-util: No DFU capable USB device available

    Target side Logs:

    U-Boot SPL 2024.04-ti-ga970f6e51043 (Nov 13 2024 - 14:26:23 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.6--v10.01.06 (Fiery Fox)')
Trying to boot from DFU
######################################################DOWNLOAD ... OK
Ctrl+C to exit ...
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Loading Environment from nowhere... OK
init_env from device 18 not supported!
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.11.0(release):v2.11.0-906-g58b25570c9-dirty
NOTICE:  BL31: Built : 04:20:32, Nov  1 2024
I/TC:
I/TC: OP-TEE version: 4.4.0-dev (gcc version 13.3.0 (GCC)) #1 Fri Oct 18 17:45:27 UTC 2024 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: GIC redistributor base address not provided
I/TC: Assuming default GIC group status and modifier
I/TC: SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.6--v10.01.06 (Fiery Fox)')
I/TC: Activated SA2UL device
I/TC: Fixing SA2UL firewall owner for GP device
I/TC: Enabled firewalls for SA2UL TRNG device
I/TC: SA2UL TRNG initialized
I/TC: SA2UL Drivers initialized
I/TC: HUK Initialized
I/TC: Primary CPU switching to normal world boot

U-Boot SPL 2024.04-ti-ga970f6e51043 (Nov 13 2024 - 14:26:23 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.6--v10.01.06 (Fiery Fox)')

    When I executed the command on the host side: sudo dfu-util -R -a tispl.bin -D tispl.bin, the target side seemed to get stuck, and the host side couldn't complete the final command: sudo dfu-util -R -a sysfw.itb -D sysfw.itb.

  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    Hello, are you still assisting with this issue? Could you please respond to the question I raised earlier?

  • 0 in reply to ? ??
    TI__Mastermind 19040 points

    Hi ? ??

    Sorry for the delay.

    This is mostly because the device tree of A72 spl(tispl.bin) could be configuring the devices that are not there in your custom board. As, I had told earlier, this issue very specfic to your custom board as on TI EVM , dfu works perfectly fine.

    Regards

    Gokul Praveen

  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    Hello Gokul Praveen,

    the device tree of A72 spl(tispl.bin) could be configuring the devices that are not there in my custom board. 

    So do you have any suggestions to help me solve this problem?

    Additionally, you did not reply to the question I raised last time.

    1. What is the function of this EEPROM chip (designator: U16)?
    2. I noticed there are also error messages related to the EEPROM in version 09.02.00.05 (released on April 8, 2024) from forum posts—so why has it become mandatory in version 10.01.00.04 (released on December 18, 2024)?
    3. Is there any way for me to operate without this EEPROM chip (designator: U16) in version 10.01.00.04 (released on December 18, 2024)?

  • 0 in reply to Gokul Praveen
    Intellectual 260 points

    Hello, are you still assisting with this issue? Could you please respond to the question I raised earlier?

  • 0 in reply to ? ??
    TI__Mastermind 19040 points

    Hi ? ??

    I found out that this was the function which was failing when EEPROM was not present on your board.

    By default, the sdk code searches for the board related data from EEPROM if CONFIG_TI_I2C_BOARD_DETECT is set to y .

    ? ?? said:
    What is the function of this EEPROM chip (designator: U16)?

    The EEPROM is used to stored board specfic information like board name, revision number etc.

    ? ?? said:
    Is there any way for me to operate without this EEPROM chip (designator: U16) in version 10.01.00.04 (released on December 18, 2024)?

    Disabling CONFIG_TI_I2C_BOARD_DETECT  will disable reading the board specific information from the EEPROM.

    I am attaching the patch for the same below.

    index 0761b82b..85e4e115 100644
--- a/arch/arm/mach-k3/j721e/Kconfig
+++ b/arch/arm/mach-k3/j721e/Kconfig
@@ -13,7 +13,6 @@ config TARGET_J721E_A72_EVM
        bool "TI K3 based J721E EVM running on A72"
        select ARM64
        select BOARD_LATE_INIT
-       imply TI_I2C_BOARD_DETECT
        select SYS_DISABLE_DCACHE_OPS
        select BINMAN
 
@@ -27,14 +26,12 @@ config TARGET_J721E_R5_EVM
        select K3_DDRSS
        select BINMAN
        imply SYS_K3_SPL_ATF
-       imply TI_I2C_BOARD_DETECT
 
 config TARGET_J7200_A72_EVM
        bool "TI K3 based J7200 EVM running on A72"
        select ARM64
        select SOC_K3_J721E_J7200
        select BOARD_LATE_INIT
-       imply TI_I2C_BOARD_DETECT
        select SYS_DISABLE_DCACHE_OPS
        select BINMAN
 
@@ -48,7 +45,6 @@ config TARGET_J7200_R5_EVM
        select K3_DDRSS
        select BINMAN
        imply SYS_K3_SPL_ATF
-       imply TI_I2C_BOARD_DETECT

    Regards

    Gokul Praveen