Author Topic: routing ethernet and the PHY  (Read 2152 times)

0 Members and 1 Guest are viewing this topic.

Offline Gibson486Topic starter

  • Frequent Contributor
  • **
  • Posts: 324
  • Country: us
routing ethernet and the PHY
« on: May 29, 2018, 06:43:23 pm »
I am routing my first ethernet board. I founds lots of guidelines online (although some conflicting, so I need to tread carefully). One thing I cannot seem to find are guidelines for the PHY to the micro. I looked at a design from ST micro with their Nucleo board for guidance. Oh my....from the PHY to the micro, they seem to just route to get there how ever possible. Does this mean that there are no guidelines from the PHY to the micro? Isn't it still a high frequency signal on the TX(0,1) and RX(0,1) lines? Are there no guidelines from the Micro to the PHY?
« Last Edit: May 29, 2018, 06:59:31 pm by Gibson486 »
 

Offline Gibson486Topic starter

  • Frequent Contributor
  • **
  • Posts: 324
  • Country: us
Re: routing ethernet and the PHY
« Reply #1 on: May 31, 2018, 12:06:16 pm »
I am gonna guess that this something I should know? or there really is a lack of documentation? or I just need to find out the hard way?
 

Offline AndyC_772

  • Super Contributor
  • ***
  • Posts: 4228
  • Country: gb
  • Professional design engineer
    • Cawte Engineering | Reliable Electronics
Re: routing ethernet and the PHY
« Reply #2 on: May 31, 2018, 12:55:29 pm »
I'm assuming that the interface you're routing is RMII.

If so, then it's designed with good timing margins, which mean there are no specific requirements for length matching. You can tell this by looking at the data sheet for the PHY and having a careful look at the setup and hold requirements; IIRC the active clock edges are in the centre of the guaranteed window where data will be valid, so they can move around a bit without causing a problem.

You need to follow general high speed layout rules, of course, but they're not specific to RMII.

Gigabit Ethernet is a different issue altogether. If you're routing GMII (or another Gbit interface), then you definitely do need to consider the contribution from the PCB when you do your static timing analysis.
 
The following users thanked this post: Gibson486

Offline Gibson486Topic starter

  • Frequent Contributor
  • **
  • Posts: 324
  • Country: us
Re: routing ethernet and the PHY
« Reply #3 on: May 31, 2018, 01:26:22 pm »
I'm assuming that the interface you're routing is RMII.

If so, then it's designed with good timing margins, which mean there are no specific requirements for length matching. You can tell this by looking at the data sheet for the PHY and having a careful look at the setup and hold requirements; IIRC the active clock edges are in the centre of the guaranteed window where data will be valid, so they can move around a bit without causing a problem.

You need to follow general high speed layout rules, of course, but they're not specific to RMII.

Gigabit Ethernet is a different issue altogether. If you're routing GMII (or another Gbit interface), then you definitely do need to consider the contribution from the PCB when you do your static timing analysis.

Thanks. RMII is correct. I had no idea what the stuff meant on the datasheet, but now I do. But yeah, I thought I needed to adhere to high speed design rules, which is why I was surprised by ST's demo board.
 

Offline bson

  • Supporter
  • ****
  • Posts: 2270
  • Country: us
Re: routing ethernet and the PHY
« Reply #4 on: June 02, 2018, 02:39:54 am »
RMII is only 50MHz.  It's not particularly sensitive.  The PHY to magnetics is 35MHz for 100M, also not particularly demanding.  It's pretty much connect the dots and done.
« Last Edit: June 02, 2018, 02:41:51 am by bson »
 

Offline tszaboo

  • Super Contributor
  • ***
  • Posts: 7388
  • Country: nl
  • Current job: ATEX product design
Re: routing ethernet and the PHY
« Reply #5 on: June 02, 2018, 07:31:46 pm »
I've  run RMII though a DIN 41612 connector, and it didn't seem to mind it. It is just a fancy multi-bit SPI . Though keep in mind, that something functional doesn't mean that it will go thorough any EMC compliance measurements. The design I made didn't need to do that.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf