This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Unable to get a dhcp ip adress on uboot for RGMII (BCM54610)

on the custom board i have built, i am using a BCM54610 Broadcom gigabit phy. I have made the mux changes on u-boot.

made sure the cpsw_slaves are in PHY_INTERFACE_MODE_RGMII mode.

But i am not able to get a dhcp ip address. Are their any specific changes i have to do get the chip working ?


is there a #define to tell the u-boot to use Broadcom driver ?

  • Hi Pradeep,

    You are trying to get ethernet working only in u-boot, or in kernel?

    Can you please share
    1. Which Sitara board are you using?
    2. Which version of u-boot are you working with? Officially released u-boot from Sitara SDK8.0 or mainline u-boot?

    For DHCP command have you tried using #define CONFIG_CMD_DHCP in your u-boot/include/configs/<board>.h? Also you can check u-boot/README file & u-boot/doc directory for some pointers.

    Best Regards,
    Yordan
  • For now i am getting it to work U-Boot (SPL 2013.01.01) I can upgrade to new one if needed

    I am using a custom AM335x board with a BCM 54610 connected to RGMII2 pins (no PHY connected to RGMII1 pins can this be a problem ?). The board is based on Beaglebone Black architecture.

    My U-boot should be based on SDK6, we dint want to upgrade to SDK 7 or 8 because of the Device tree (most of us are yet to get a grasp of it).

    But i guess there is no Device tree architecture in U-boot be it SDK7 or SDK8 (right ??)

    and strangely when i probe the board i do see activity on the rd0 to rd3, rctl and rclk but only see tclk with no activity on tctl or td0 to td3.

    Change i have done so far

    * added pinmux for rgmii2 on mux.c
    * forced cpsw_slave to be inited with PHY_INTERFACE_MODE_RGMII on board.c
    * made the get_phy_device in miiphy_reset to use PHY_INTERFACE_MODE_RGMII (this is in phy.c)
  • Hi Pradeep,

    Sorry for the delayed response.

    Pradeep Deepu said:
    But i guess there is no Device tree architecture in U-boot be it SDK7 or SDK8 (right ??)

    Correct, u-boot does not use device tree. You can try using either the latest TI u-boot (from SDK8.0) or the latest mainline u-boot from denx.de

    Also can you try defining the broadcom driver (located in  u-boot/driver/phy) along with
    #define CONFIG_PHY_GIGE
    #define CONFIG_PHYLIB
    #define CONFIG_PHY_SMSC
    in the am335x_evm.h file. The CONFIG_PHY_SMSC defines the LAN87XX PHYs: http://lists.denx.de/pipermail/u-boot/2011-November/111028.html

    Best Regards,
    Yordan