Community
cancel
Showing results for 
Search instead for 
Did you mean: 
idata
Community Manager
1,467 Views

i210 flash image with PXE sector gets corrupted when programmed via eeupdate efi util

Running into the following issue:

Programmed i210 custom image (Dev_Start_I210_Copper_NOMNG_16Mb_A2_3.25_0.03 with PXE bootrom option added to flash config binary) via efi shell eeupdate util version 5.25.20.03.

On certain test units, after some power cycles the following message would appear at BIOS splash screen

BIOS reported the "PXE-05: The LAN adapter's NVM configuration is corrupted or has not been initialized." error message

 

I checked CRC via eeupdate /gui option eeprom test and it fails.

Does this mean there is a flash corruption after it was programmed with eeupdate util?

0 Kudos
6 Replies
idata
Community Manager
272 Views

Another thread indicated that the flash images need to be signed. How do l verify the image l am using is signed?

Gabriel_T_Intel
Employee
272 Views

Hello Eduard,

Welcome to the Intel Embedded Community.

We will contact you as soon as possible.

Regards,.

Gabriel Thomas

Adolfo_S_Intel
Moderator
272 Views

Hello # EdP

Please provide the following information:

1) What NVM model are you using?

2) Where are you mergint the PXE on the BIOS or on the NVM?

3) What tools are you using to build your PXE image and What PXE image version are you using?

4) Who is your BIOS vendor? Have you consulted this case to them? By the way make sure that you are using the latest BIOS update

5)Do you have problems just during PXE phase? Does the device works well if working under O.S.?

Regarding your doubts about signature, please check section 3.3.10 Flash Security of the I210 Datasheet: http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/i210-ethernet-controller-data... http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/i210-ethernet-controller-data...

I will be waiting for your feedback,

Best Regards,

Adolfo Sanchez

idata
Community Manager
272 Views

1) What NVM model are you using?

Spansion SPI flash S25FL116K0XNFI011

2) Where are you mergint the PXE on the BIOS or on the NVM?

PXE merged on the NVM at offset 2000 - 12FFF

3) What tools are you using to build your PXE image and What PXE image version are you using?

Flash image with PXE add-on was provided by Intel. I can provide that to you by email if you want to review it.

Version reported from BIOS splash screen:

Initializing Intel(R) Boot Agent GE v1.5.43

PXE 2.1 Build 092 (WfM 2.0)

4) Who is your BIOS vendor? Have you consulted this case to them? By the way make sure that you are using the latest BIOS update

AMI version 2.15.1236, not consulted with them yet as it was believed to be a PXE option programming related issue so far.

5)Do you have problems just during PXE phase? Does the device works well if working under O.S.?

We are not booting from PXE. Device does show programmed and working under OS. We are trying to understand why this message appears and eeupdate reports image in flash to fail CRC check. Also when problem flash is re-burned via an extracted eep image via the /gui method in eeupdate from a known good flash the issue does not seem to happen again. It seems so far to only happen when programming flash for the first time via eeupdate efi util.

Adolfo_S_Intel
Moderator
272 Views

Hello Eduard

We are still working on your issue, and will provide more information as soon as posible

Best Regards,

Adolfo

Adolfo_S_Intel
Moderator
272 Views

Hello # EdP

As you can see on the i210 datasheet: http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/i210-ethernet-controller-data... http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/i210-ethernet-controller-data..., section 11.8.1 you are no using one of our recommended Flash Parts so this could be a factor on your problem. If possible try testing with one of our supported Flash Parts.

I also got the following feedback from our Engineers:

"When PXE executes, it checks the PXE version number in word 0x32 of the NVM. If it does not match the version that is running, it will correct the value and write it to the NVM, which also entails correcting the checksum value in word 0x3F. This sounds like it is having trouble writing the checksum. This would indicate a problem writing to the flash component."

Please check the value of 0x3F and 0x32 before and after booting.

How many boards do you have? All the boards show the same behavior?

The LAN engineers also suggest that you use Intel Premier Support Service: https://software.intel.com/en-us/faq/premier-support https://software.intel.com/en-us/faq/premier-support, I checked and your company already have an account on that service so I would suggest contacting your Intel FAE to request access to that service.

I will be waiting for your feedback.

Best Regards,

Adolfo Sanchez

Reply