![]() ![]() Once we fixed our HW problems, the i210 and the switch were able to communicate. Your suggestion to use the SERDES/KX firmware was correct. Is this another way to set a MAC address if the flash cannot be written? I am not concerned about users modifying this value. I notice that the properties pages for the driver (in Device Manager) allow a "Locally Administered Address" to be defined. Maybe I will have better luck with the SERDES firmware. Once power was cycled, the original MAC address was active. The MAC address (and checksum) were updated in the shadow EEPROM, but flash was not re-written. On another topic that I mentioned earlier, although I have not tried to write a MAC address to flash with the SERDES firmware loaded, I was not able to do this when the SGMII firmware was in use. Does this mean that you believe that the SERDES firmware will not support the 88E6097F? I will have a look at Marvell's datasheet for this part and see what it reveals. I have also seen another comment from you that the Intel drivers only support the 88E1111. We will fix this on Monday and I will provide an update. Unfortunately, our Marvell switch is inoperable at the moment due to HW problems. ![]() I programmed the i210 with the SERDES firmware and the driver now recognizes the device (Device ID 0x1537) and starts up properly. If you need any more information or want me to perform some tests, please don't hesitate to ask. If there is any step that I have overlooked, please let me know.Īny assistance would be most appreciated. I have compared our schematic with the reference one and the only difference is that we have pulled the SECURITY_EN (NVM_SI) signal low to facilitate development.įrom the comments I see in other discussions, it seems that programming the firmware was sufficient to get the i210 up and running. I can use lanconf to inspect the internal registers of the i210. The lanconf tool shows that the PCI registers have been initialized. Our system also has an i218-LM in it and that part functions properly (the driver supports both of these devices). This all seems good, but when I install the driver the i210 is recognized and the driver is installed, but in Device Manager the i210 is non-functional and the reason given is "the device won't start (error 10)". Inspecting it using lanconf shows that it is uninitialized. EEUPDATE also confirms that the flash checksum is good.Īs a double-check, I used the lanconf tool to verify that the image data is present in both flash and shadow EEPROM. I have verified using EEUPDATE that the device can be found and has a PID of 0x1538. I am using the latest versions of both the tools and firmware (both downloaded from Intel in the last couple of days). ![]() I have not attempted to modify the image in flash in any way (not even changing the MAC address - which I can't do either, but that's another problem). I have programmed the i210 with the file Dev_Start_I210_Sgmii_NOMNG_16Mb_A2_3.25_0.03.bin (the flash is Microchip SST25VF016B - a 16 Mbit part). Our development platform is 64-bit Windows 7 Embedded. SGMII is the interface between these two devices. We're developing an Ethernet NIC based on the i210-IS and the Marvell 88E6097F (a multi-port switch). # the memory map information from GRUB (GNU Mach, kernel of FreeBSD. # This works with Linux (no patch required) and with any kernel that obtains # Uncomment to enable BadRAM filtering, modify to suit your needs GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` ![]() # For full documentation of the options in this file, see: However, there is no such line in the file, which sole content is: # If you change this file, run 'update-grub' afterwards to update I've read about the matter and what I found was advice to comment the following line out of the grub file: GRUB_HIDDEN_TIMEOUT=0 However, I'd like to still have the grub option so I can switch between kernels, and I want to make it permanent. So, I had a dual boot and just nuked the windows partitions, and then got rid of the boot files for windows and updated the grub, and now my PC boots directly into ubuntu. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |