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.

LP-AM243: The problem of 100M PHY replacement on LP-AM243 development board

Part Number: LP-AM243
Other Parts Discussed in Thread: DP83869,

Hi Experts,

    

My customer want to use the 100M/PHY by use the Sitara MCU, like the DP83822.

They took a fancy to the AM243x chip, and they want just They want to directly replace the DP83869 on the development board with the DP83822. Is it feasible?

What needs to be modified on the current SDK? and is it supported on the hardware? Thanks!

  • Hi Shaoxing,

    Unfortunately, the DP83822 and DP83869 have different packages, so the PCB footprints are not compatible and you cannot swap it out on the LP-AM243.  You would need to have a custom board built for the application.

    From an SDK perspective, the SDK notes say the current version of the ENET LLD  in SDK v08.01.00 supports a generic Phy driver, as well as the DP83867, DP83869, DP83822, and VSC8514 phy drivers.

    Thanks,
    Mike

  • From an SDK perspective, the SDK notes say the current version of the ENET LLD  in SDK v08.01.00 supports a generic Phy driver, as well as the DP83867, DP83869, DP83822, and VSC8514 phy drivers.

    Hi Mike,

         Do you mean that the software SDK itself supports it without any modification? Will different PHY chips affect the power-on initialization of the PHY?

  • Hi Shaoxing,

    The SDK notes list the above Phys as supported.  Likely, there will be some minor changes necessary to the SDK implementation to select the appropriate Phy, but you should not have to make major modifications to the software to enable support.

    On the LaunchPad, the power on sequencing for the phy is all determined by hardware.  The three rails (VSYS_3V3, VDD_2V5, and VDD_1V1) and are powered on in the following sequence:

    • VSYS_3V3 is generated from the VSYS_5V0 (comes from 5V on USB-C plug), and is enabled by the BOARD_POWER_EN signal (normally pulled high to VSYS_5V0)
    • VDD_2V5 is generated from VSYS_3V3, and is enabled by the VSYS_3V3 rail
    • VDD_1V1 is generated from VSYS_3v3, and is enabled by the VSYS_3V3 rail

    Because the power sequencing is all done in hardware on the LaunchPad, changing the Phy will not change the the power on sequencing.

    Thanks,

    Mike

  • The SDK notes list the above Phys as supported.  Likely, there will be some minor changes necessary to the SDK implementation to select the appropriate Phy, but you should not have to make major modifications to the software to enable support.

    Hi Mike,

         you mentioned that the minor changes, which point to the SDK? Suppose that my customer will use the PN/RT_MII example.

         can you help to clarify that the minor changes?

  • Shaoxing
    Right now, only DP83869 PHY is supported in MCU+ SDK. Custom PHY support is planned for future releases.

    Regards
    Dhaval Khandla