PHY: Don't process Manchester timing right from the start #2

Closed
opened 2021-09-04 19:13:43 +02:00 by markus · 1 comment

After the first edge on the input, we should wait for a few cycles before we start actually looking at the data.

Glitches at the beginning (caused by to us coming out of zero-glitching-zone) may cause us to either incorrectly detect a SOF oder bit error (which will reject the entire telegram.)

After the first edge on the input, we should wait for a few cycles before we start actually looking at the data. Glitches at the beginning (caused by to us coming out of zero-glitching-zone) may cause us to either incorrectly detect a SOF oder bit error (which will reject the entire telegram.)
markus added this to the PHY + MAC milestone 2022-01-09 20:52:41 +01:00
markus changed title from Don't process Manchester timing right from the start to PHY: Don't process Manchester timing right from the start 2022-01-16 14:45:59 +01:00
Poster
Owner

Fixed in a different way in 61812c133f.

Fixed in a different way in 61812c133fe67bf3404cc9fc4bded0ea78b85b24.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: fpga/trashernet#2
There is no content yet.