- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We have a new board with three unprogrammed i210-AT network chips, and are having trouble programming and verifying them. I guess that I must be missing a step somewhere.
I did a dump from an i210 adapter that was from another supplier and is working, to use that to program the EEPROM.
I then have successfully programmed the EEPROM and MAC id for one of the chips, however when I run the EEPROM test I still get an invalid checksum.
Please advise.
$ sudo ./eeupdate64e -NIC=4 -D ./XXXXXXXXXXXX.bin
[sudo] password for v4:
Using: Intel (R) PRO Network Connections SDK v2.37.28
EEUPDATE v5.37.28.00
Copyright (C) 1995 - 2021 Intel Corporation
Intel (R) Confidential and not for general distribution.
NIC Bus Dev Fun Vendor-Device Branding string
=== === === === ============= =================================================
1 0 31 06 8086-15B7 Intel(R) Ethernet Connection (2) I219-LM
2 5 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection
3 6 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection
4 8 00 00 8086-1531 Intel(R) I210 Blank NVM Device
5 9 00 00 8086-1531 Intel(R) I210 Blank NVM Device
6 10 00 00 8086-1531 Intel(R) I210 Blank NVM Device
Writing SHARED FLASH. PLEASE DO NOT INTERRUPT THIS PROCESS.
4: Shared Flash image updated successfully.
$ sudo ./eeupdate64e -NIC=4 -MAC=XXXXXXXXXXXX
Using: Intel (R) PRO Network Connections SDK v2.37.28
EEUPDATE v5.37.28.00
Copyright (C) 1995 - 2021 Intel Corporation
Intel (R) Confidential and not for general distribution.
NIC Bus Dev Fun Vendor-Device Branding string
=== === === === ============= =================================================
1 0 31 06 8086-15B7 Intel(R) Ethernet Connection (2) I219-LM
2 5 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection
3 6 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection
4 8 00 00 8086-1531 Intel(R) I210 Blank NVM Device
5 9 00 00 8086-1531 Intel(R) I210 Blank NVM Device
6 10 00 00 8086-1531 Intel(R) I210 Blank NVM Device
4: Updating Mac Address to 70B3D5D01033...Done.
4: Updating Checksum and CRCs...Done.
$ sudo ./eeupdate64e -NIC=4 -test
Using: Intel (R) PRO Network Connections SDK v2.37.28
EEUPDATE v5.37.28.00
Copyright (C) 1995 - 2021 Intel Corporation
Intel (R) Confidential and not for general distribution.
NIC Bus Dev Fun Vendor-Device Branding string
=== === === === ============= =================================================
1 0 31 06 8086-15B7 Intel(R) Ethernet Connection (2) I219-LM
2 5 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection
3 6 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection
4 8 00 00 8086-1531 Intel(R) I210 Blank NVM Device
5 9 00 00 8086-1531 Intel(R) I210 Blank NVM Device
6 10 00 00 8086-1531 Intel(R) I210 Blank NVM Device
4: EEPROM test failed: Incorrect Checksum
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, @donatello:
Thank you for contacting Intel Embedded Community.
You should review that the affected designs fulfill the requirements that are stated as answers to questions 2.14, 2.15, 2.23, and 2.25; on pages 8 and 9 of the document stated on the following website:
https://cdrdv2.intel.com/v1/dl/getContent/334026
Best regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Carlos,
Thanks for your reply. I will discuss this with my colleague and come back to you.
Have a Merry Christmas, if I don't correspond before then!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm sorry, I made a mistake. The board we designed is using i210-IT network chips, not i210-AT as stated previously.
Please can you point me to the correct version of the documentation?
So far I'm only finding i210-AT related stuff...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
It turns out that this board does have the WGI210AT, as originally proposed (some people at this end causing confusion!).
I'm still not clear why the checksum is invalid.
Answers to your points:
2.14 use the appropriate text file - we used binary.
2.15 EEUPDATE was used.
2.23 security - checked OK
2.25 Changes not active until a power cycle - was done
--------------------------
[v4@localhost MAC]$ sudo ./eeupdate64e -NIC=4 -test
Using: Intel (R) PRO Network Connections SDK v2.37.28
EEUPDATE v5.37.28.00
Copyright (C) 1995 - 2021 Intel Corporation
Intel (R) Confidential and not for general distribution.
NIC Bus Dev Fun Vendor-Device Branding string
=== === === === ============= =================================================
1 0 31 06 8086-15B7 Intel(R) Ethernet Connection (2) I219-LM
2 5 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection
3 6 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection
4 8 00 00 8086-1533 Intel(R) I210 Gigabit Network Connection
5 9 00 00 8086-1531 Intel(R) I210 Blank NVM Device
6 10 00 00 8086-1531 Intel(R) I210 Blank NVM Device
4: EEPROM test failed: Incorrect Checksum
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, @donatello:
Thanks for your replies.
The suggested document is related to all the Intel i210 Ethernet Controllers.
You should review it.
Best regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
1. I have attached a text version of the ".eep" from the valid i210, whose binary file I used to program the EEPROM, in case that has any clues. Could it be something to do with different chip vendors?
2. Also, I ran nvmupdate64e using the inventory mode, and the chip I have partially programmed shows "LAN MAC" is different to "Alt MAC", while the valid i210 has them being identical.
Is this why I'm getting the invalid checksum and how do I fix it?
Is using the "eeupdate64e" tool no longer valid?
Thanks again for you help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, @donatello:
Thanks for your reply.
We sent an email to the address related to your account with information that may help you.
Best regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Carlos,
Please can you try and resend the information, it hasn't come through to my email. Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @CarlosAM_INTEL ,
Please can you try and resend the information, it hasn't come through to my email.
I didn't see it in my spam either, so not sure what's happened.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, I use the I210-IT on my board now , I encoutered the same problem.
Can you send the EEUPDATE tool and the to me?
Is there other things to note when program the flash on board?
And EEUPDATE is used in DOS or Windows?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, @Meling:
Thank you for contacting Intel Embedded Community.
You need to have a Resource and Design Center (RDC) privileged account to have access to the information that may help you.
The RDC Account Support form is the channel to process your account update process by filling out the form stated on the following website:
https://www.intel.com/content/www/us/en/forms/support/my-intel-sign-on-support.html
You should use a business email address to evade any inconvenience. Please avoid the free email provider's address (such as the provided by Hotmail, Gmail, Yahoo, or others).
By the way, could you please clarify if this thread is related to the following forum?
https://community.intel.com/t5/Embedded-Connectivity/WGI210IT-Device-ID-issue/m-p/205228#M563
Best regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, @donatello:
Thanks for your updates.
We resent an email to the address related to your account with information that may help you.
Best regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hi
we have the same problem as donatello.
Can you please send me either the email you wrote to donatello?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @Kowaltksi,
Thank you for contacting Intel Embedded Community.
My apologies as I don't have access to that email to share it with you but maybe is referring to IPS:
https://www.intel.com/content/www/us/en/support/articles/000057045/ethernet-products.html
If you are having troubles with the NVM you may try checking section "2.0 Pin Interface" from the datasheet, to make sure that everything is well configured, like the pin 14 is pulled up.
Also, you can check the following in RDC:
-NVM Update from #348742 - Intel® Network Connections Tools 28.3 PV LAN Software Tools.
-#572162 - EEPROM Access Tool [EAT].
-#513655 - Intel® Ethernet Controller I210 and I211- AT Production NVM Images.
Best regards,
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page