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.