This tutorial assumes the user is connecting the EVM to the ASPEED AST2600 Evaluation Board (EVB).

1. Building the image to flash onto the ASPEED processor
   1. Follow the steps in the README at this GitHub repository to build the image on a Linux machine.
   2. Also, please consult the README at this GitHub repository for additional flashing information. Install the packages listed in both README files.
   3. Build the image on your Linux machine.

2. Editing the image

   1. There are a series of steps to modify the default image so it integrates the necessary PHY drivers.

   2. First, open the following file:

      1. [BUILD_DIR]/openbmc/build/evb-ast2600/tmp/work/evb_ast2600-openbmc-linux-gnueabi/u-boot-aspeed-sdk/v2019.04+git/git/drivers/phy/Kconfig
   3. Then, edit the Kconfig file by adding the lines circled below.
      
   4. Second, add the DP83867 and DP83869 driver files to the proper directory.
      1. Open this TI-maintained repository and copy the DP83867.c and DP83869.c files.
      2. Paste the files in the following directory:
         1. [BUILD_DIR]/openbmc/build/evb-ast2600/tmp/work/evb_ast2600-openbmc-linux-gnueabi/u-boot-aspeed-sdk/v2019.04+git/git/drivers/net/phy
   5. Third, edit the Makefile in the U-Boot layer.
      1. Open the file called “Makefile” in the same directory as the above step.
      2. Make the following additions:
         

   6. Fourth, change the U-Boot layer defconfig file.

      1. First, open the following file:
         1. [BUILD_DIR]/openbmc/build/evb-ast2600/tmp/work/evb_ast2600-openbmc-linux-gnueabi/u-boot-aspeed-sdk/v2019.04+git/git/configs/evb-ast2600_defconfig
      2. Then, add the following lines to the file:
         

   7. Fifth, edit the U-Boot layer device tree file.

   8. Sixth, enable the mactest utility by following the instructions in ASPEED's User Guide. Please contact ASPEED for this information.
   9. Seventh, edit the Linux layer defconfig file.
      1. Open the following file:
         1. [BUILD_DIR]/openbmc/meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig
      2. Add the following lines:
         
   10. Finally, rerun the bitbake command below which regenerates the build image. Please note that you must be in the correct directory to run this command as specified by the README mentioned here.
       1. bitbake obmc-phosphor-image
3. Flashing the image
   1. Please follow ASPEED’s documentation regarding how to flash the ASPEED processor on the AST2600 EVB. This involves using the Firmware Utility. Please reach out to ASPEED for this documentation.
   2. Also, please note that you must use a special cable to connect the ASPEED EVB to your PC.
      1. This cable must be a female RS232 to USB cable with internal crossover. Effectively, this cable mirrors the signals internally similar to how the TX pin of a device is connected to the RX pin of another device and vice verse.
   3. Lastly, the MAC interface signals on the ASPEED EVB needs to be rerouted by manually desoldering resistors on the EVB and moving them to new footprints. Please refer to ASPEED’s documentation for information about which resistors to resolder to steer the MAC signals to the BergStak connector.
4. Checking for Successful Driver Binding to the PHYs
   1. During the booting process the user can see boot-up information printed out in the Tera Term console. Make sure that the right COM port is active in the Tera Term console and that all serial settings (baud rate, stop bit, parity, etc.) are set to the right values according to ASPEED's documentation. Once bootup is complete, run the following command: grep | dmesg “mdio”
   2. Then, make sure that the output of the command matches the output below to confirm that the Ethernet PHY drivers have been properly bound.
      
   3. If the drivers have been properly bound, the user can begin basic testing.