Thank you for contacting Intel.
For corrupted Eeprom, reflashing the image may recover the controller. Please refer to this article on how to update the boot agent.
Hope this is helpful. If you continue to encounter this error, we suggest to contact your system manufacturer for assistance.
I am more interested in finding root cause of the problem as there is a lot of device on the field is affected.
Once the Vendor ID/Subsystem ID overwritten by zero the device is not recognized and I saw no chance in this case to update the EEPROM. (We are speaking about SW solutions, replacing the CPU module all the time is not so cost effective).
As I saw only bytes overwritten by zero bytes (compared to the golden image) it means that the EEPROM programmed somehow (as everybody know 0xFF erased, not 0xFF programmed state).
So if it would be noise then I should see not just zero bytes, but other random stuff.
As only Intel is responsible for writing the driver I would need some assistance from them.
Speaking with the system manufacturer about SW/driver is just increasing the message passing nodes by 2-3 and reducing the speed of effective problem solving.
Thats why I am asking community also whether thay have met with the same problem yet or not.
Thanks for writing back. I'll help check on this.
ok, thank you in advance!
Ah yes, one more additional info: we are using a non-manageable image: MNGM=00.
Thanks for your reply.
Upon checking, we recommend to contact your system manufacturer. Because integrating and configuring these controllers differs between different manufacturers to customize the boards.
However, if you would like us to check on this, kindly contact our Customer Support team. Please find contact details below:
Have a great weekend!