Greetings,
I have a new design that includes my prototype baseboard which has an i210-it and a Qseven CoM that includes an E3815 Atom and an i210. I'm following the directions from document 513655 to program the blank flash for my baseboard's i210. Running EEUPDATE shows my two i210 controllers (one working, and one blank). Using both EEUPDATE & LANConf to attempt to program the blank flash results in a timeout error that occurs after 5+ minutes of the tool claiming that it is writing to flash.
LANCOnf gives the following: c86a0004 - "Timeout Error" when programming i210 blank flash
I'm using the following versions on an Intel Atom E3815 processor on Ubuntu 16.04.2
eeupdate64e: EEUPDATE v5.26.17.11
lanconfig64e: LANConf v1.26.17.11
lshw shows the driver as: driver=igb driverversion=5.3.0-k
I've tried flashing with multiple 4Mb files onto a 4Mb flash On Semi LE25U40CMC
Below is the eeupdate log:
_________________________________________________________
root@ubuntu-serv-slim:/# ./eeupdate64e /NIC=1 /DATA Dev_Start_I210_Copper_NOMNG_4Mb_A2_3.25_0.03.bin
Using: Intel (R) PRO Network Connections SDK v2.26.17
EEUPDATE v5.26.17.11
Copyright (C) 1995 - 2015 Intel Corporation
Intel (R) Confidential and not for general distribution.
Driverless Mode
NIC Bus Dev Fun Vendor-Device Branding string
=== === === === ============= =================================================
1 2 00 00 8086-1531 Intel(R) I210 Blank NVM Device
2 4 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection
Writing SHARED FLASH. PLEASE DO NOT INTERRUPT THIS PROCESS.
1: Shared Flash image update FAILED! Timeout Error
_____________________________________________________
Things I've learned in debugging:
1) I can program the flash off board and then the I210 is recognized.
2) After flashing off board, EEUPDATE can reprogram the flash using the same file that timed out originally including update the check sum.
Is there some bit that needs to be set or a flag to allow for programming blank flash? Does is need a MAC address first? I'm sure it's something simple/stupid but any help you can provide is appreciated.
Enjoy,
Jason
p.s. This was originally posted in "Wire Ethernet" and was requested to move to embedded.