Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Ok, i've read the release and component notes for the MDIO. nice job.
this is only part of an MII/RMII solution. is the other coming very soon or do we start to roll our own? do we think a set of UDBs ( 2 or 4?) can keep up with 25/50Mhz ethernet traffic needed for MII/RMII? by the time we are done a full MII/RMII how many UDBs will be used up? will we have any left to do any work with the data?
The most typical usage of the MDIO Interface component will be in modules that implement the CFP MSA Hardware standard for 40 Gbps and 100 Gbps optical modules. The specification for those optical modules uses the MDIO interface standard for management of the module. This type of equipment can benefit from a programmable solution to implement this interface and a description of that implementation is shown starting on page 17 of the Data sheet in the Functional Description. The previous page has references to the applicable CFP MSA Specifications. For this very high speed equipment the data traffic certainly will not be going through the PSoC device.
For standard 100 Mbps Ethernet data interfaces that you describe (MII/RMII) the MDIO interface for those connects to the Ethernet Phy and would already be integrated into those devices.
There has been some discussion in the forum about support for 10 Mbps Ethernet support directly in PSoC (Ethernet Component). That work is ongoing.