Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

  • State
  • Replies 1 reply
  • Subscribers 101 subscribers
  • Views 37 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

AM623: Request to Remove EEPROM-Related Log Messages from System

Murali Vikash Ganireddy
Intellectual 420 points
Part Number: AM623

Tool/software:

Hi,

We are using AM623 custom board in our project, but our board design does not include an EEPROM component. Despite this, we are observing EEPROM-related log messages during the boot process or operation. These logs are unnecessary in our setup and cause confusion during debugging.

Could you please guide us on how to suppress or remove these EEPROM-related messages from the system logs? If any configuration changes, kernel modifications, or device tree updates are needed, kindly provide detailed instructions.

U-Boot SPL 2023.04-ti-gf9b966c67473 (Mar 19 2024 - 20:31:40 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.7--v09.02.07 (Kool Koala)')
SPL initial stack usage: 1856 bytes
** Bad device specification mmc 1 **
Couldn't find partition mmc 1:1
Error: could not access storage.
Trying to boot from MMC1
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


U-Boot 2023.04-ti-gf9b966c67473 (Mar 19 2024 - 20:31:40 +0000)

SoC:   AM62X SR1.0 GP
Model: Texas Instruments AM625 SK
EEPROM not available at 80, trying to read at 81
Reading on-board EEPROM at 0x51 failed -121
DRAM:  no bloblist found!2 GiB
Core:  65 devices, 30 uclasses, devicetree: separate
MMC:   mmc@fa10000: 0
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
EEPROM not available at 80, trying to read at 81
Reading on-board EEPROM at 0x51 failed -121
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0
switch to partitions #2, OK
mmc0(part 2) is current device

Regards, vikash

  • 0
    TI__Genius 12290 points

    Hi Vikash,

    The U-boot code prints the status of EEPROM if the config option TI_I2C_BOARD_DETECT is enabled.

    #if CONFIG_IS_ENABLED(TI_I2C_BOARD_DETECT)
int do_board_detect(void)
{
	int ret;

	ret = ti_i2c_eeprom_am6_get_base(CONFIG_EEPROM_BUS_ADDRESS,
					 CONFIG_EEPROM_CHIP_ADDRESS);
	if (ret) {
		printf("EEPROM not available at 0x%02x, trying to read at 0x%02x\n",
		       CONFIG_EEPROM_CHIP_ADDRESS, CONFIG_EEPROM_CHIP_ADDRESS + 1);
		ret = ti_i2c_eeprom_am6_get_base(CONFIG_EEPROM_BUS_ADDRESS,
						 CONFIG_EEPROM_CHIP_ADDRESS + 1);
		if (ret)
			pr_err("Reading on-board EEPROM at 0x%02x failed %d\n",
			       CONFIG_EEPROM_CHIP_ADDRESS + 1, ret);
	}

	return ret;
}

    Please check where this config is used, and remove it.

    Re-build the U-boot source code and try again.

    Regards,
    Aparna