• State
  • Locked Locked
  • Replies 10 replies
  • Subscribers 100 subscribers
  • Views 1042 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.

AM6412: Reading on-board EEPROM at 0x50/0x51 failed -19 error during boot

Jason Reeder
Genius 10440 points

Part Number: AM6412

We are trying to supress error logs "Reading on-board EEPROM at 0x51 failed -19" from u-boot while AM64X is booting up. As this is u-boot source code we want to eliminate any fix with ripple effect scenarios.

We configured chip address 0x50, , initially we log errors but in a53 u-boot we read details from device correctly.

Error log shows ret=-19 which clarifies the bus is not yet initialized or busy. 

#define ENODEV 19 /* No such device */

Fix we applied is in do_board_detect(), using  flag GD_FLG_DEVINIT which helps in determining the device is completely initialized or not. Only when device is initialized, we are reading the bus, and this suppress the issue for us. But we would like to know your opinion on this before checking in this fix.  Attached the fix patch here: /cfs-file/__key/communityserver-discussions-components-files/791/0013_2D00_Delaying_2D00_reading_2D00_EEPROM_2D00_before_2D00_device_2D00_initialization.patch.