We have a board of our own design with an Intel 82574 ethernet controller connected to a SST25VF040B serial flash. We have programmed the flash with the image available at document # 377520, altering only the MAC address, LED settings, and checksum. When we boot into u-boot, the ethernet controller is recognized by the e1000 driver (and displays the correct MAC address, so we know the flash was programmed correctly), but the driver times out whenever it tries to run auto-negotiation. Is this a known issue?
We're also curious whether there is a way to read/write the PHY registers from u-boot. Using `pci display` we have only been able to read the NVM settings.
Thank you for contacting Intel Embedded Community.
In order to be on the same page, could you please tell us if the affected design has been reviewed by Intel?
Could you please let us know the procedure and the tools that you have used to flash the image in the affected device?
Could you please clarify if this consultation is related to the Carlos_A.
Our design is not reviewed by Intel, but we followed the reference schematics when designing it.
We programmed the flash by soldering wires to the flash, connecting them to an https://learn.adafruit.com/adafruit-ft232h-breakout/overview FTDI chip, and writing over the SPI interface (following the protocol specified by the flash's datasheet). We have verified that the flash was programmed properly by reading back what we wrote from the flash. We can also tell it was written because u-boot shows the MAC address that we programmed.
This consultation is not related to our previous thread.
Thanks for your reply.
Based on your previous communication, could you please verify if the problem persists when you follow the guidelines stated in section 3.3.8; on pages 58, 59, and 60 of the https://www.intel.com/content/dam/doc/datasheet/82574l-gbe-controller-datasheet.pdf Intel(R) 82574 GbE Controller Family Datasheet?
Waiting for your update.
We cannot try the procedure specified in the section 3.3.8 as we are in u-boot and not in linux. Until we fix the ethernet issue in U-boot, we cannot install linux as this is the primary ethernet interface for our board.
We are sure that we programmed the flash correctly as we were able to read back multiple times even after power cycling through the FTDI chip. The fact that we are able to read the programmed Mac address through u-boot, tells us that we programmed the flash correctly.
Thanks for your clarification.
We suggest you as a reference please review the information stated at the following website and please address your U-Boot consultations to channels stated at:
By the way, please send the affected design to be verified by the Intel Schematic and Layout Service. The procedure to do this can be found at the following website:
We hope that this information may help you.