Honored Contributor
Honored ContributorHi again,
To further explain my point: The Tx guy must send you data according to an agreed format(protocol). There are several scenarios. For example: Tx may send 10 channels. Each channel will have its own bursty rate. But Tx will have to manage passing all data from their clock domains to the link (using various fifo techniques). Tx may need to pass data as packets with extra headers to indicate its start and which bytes are valid. Tx may stuff the idle slots with a pattern e.g.(01010101) and the packet header may be the values(4=> 3 => 2 => 1 => go...) The Rx can use these patterns to lock to the stream and detect packet/byte boundaries and then read valid data(once it receives the recovered raw bytes and its clock). Thus Rx reads the data that are valid only... Kaz
