Community
cancel
Showing results for 
Search instead for 
Did you mean: 
MSchl5
Beginner
1,430 Views

EEUpdate /verify seems unreliable

We are trying to find a way to verify that eeupdate has actually updated the i210 NIC fw after it says it succeeded.

As part of my investigating, I have attempted to use /verify immediately after flashing the fw, as well as after power cycling the unit (20+ seconds). eeupdate /verify pretty much always reports an error of some sort.

I have done pretty much the same thing in WinPE10 32-bit, WinPE10 64-bit, and EFI-shell with different versions of the tools, with basically the same results.

X:\Temp\i210-FwUpdate>EEUPDATEW32.exe /nic=2 /d I210_Ver.3.25_20171012.bin

Using: Intel (R) PRO Network Connections SDK v2.32.12

EEUPDATE v5.32.12.00

Copyright (C) 1995 - 2018 Intel Corporation

Intel (R) Confidential and not for general distribution.

NIC Bus Dev Fun Vendor-Device Branding string

=== === === === ============= =================================================

1 5 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection

2 6 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection

3 7 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection

4 16 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection

Writing SHARED FLASH. PLEASE DO NOT INTERRUPT THIS PROCESS.

2: Shared Flash image updated successfully.

X:\Temp\i210-FwUpdate>EEUPDATEW32.exe /all /verify I210_Ver.3.25_20171012.bin

Using: Intel (R) PRO Network Connections SDK v2.32.12

EEUPDATE v5.32.12.00

Copyright (C) 1995 - 2018 Intel Corporation

Intel (R) Confidential and not for general distribution.

NIC Bus Dev Fun Vendor-Device Branding string

=== === === === ============= =================================================

1 5 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection

2 6 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection

3 7 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection

4 16 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection

1%1: Image Verification Test Failed - Flash verify error at offset 0x4

1%2: Image Verification Test Failed - Flash verify error at offset 0x4

3: Image Verification Test Failed - Flash read error at offset 0x64

1%4: Image Verification Test Failed - Flash verify error at offset 0x0

Am I doing something wrong? Do I have an incorrect understanding of how /verify should work?

Are there different tools for different x86-64 CPUs such as Core i5 vs. ApolloLake vs. Kaby lake? I'm assuming the same tools work across these CPUs.

0 Kudos
3 Replies
CarlosAM_INTEL
Moderator
243 Views

Hello, ftms:

Thank you for contacting Intel Embedded Community.

Based on your previous communication, could you please clarify if the affected project has been manufactured by you or by a third-party company? In case that it is a third-party device, could you please give us the part number, model, and where to find its documentation?

Thanks in advance for your cooperation.

Best regards,

Carlos_A.

MSchl5
Beginner
243 Views

The i210 NICs are in a MB manufactured for us by our vendor.

CarlosAM_INTEL
Moderator
243 Views

Hello, ftms:

Thanks for your clarification.

Based on your communications, could you please verify that your implementation fulfills with the requirements stated in the answers to the questions 2.14, 2.15, 2.16, and 2.23; on pages 8 and 9 of the https://www.intel.com/content/dam/www/public/us/en/documents/faqs/ethernet-controller-i210-i211-faq.... Intel(R) Ethernet Controller I210/I211 Frequently Asked Questions [FAQs] document # 335346?

Could you let us know the sources that you have used to implement the affected design? By the way, could you please tell us if it has been reviewed by Intel?

Waiting for your reply to these questions.

Best regards,

Carlos_A.

Reply