It looks like there is a absolute timing dependency between the DATA_P and DATA_N signals, are you sure that you will be able to interpret the data correctly with the PIC controller? Is there are way in a PIC controller to get a timing relationship between two captured serial streams?
Right and there is result pair per ASIC, that's a lot of data for a micro analyse in real time. Perhaps a CPLD in front of the PIC would be smart?
Looking at the protocol specification...DATA_P and DATA_N don't have to be 100% synchronous. The protocol indicates a transition period of *at least* 125ns (250ns respectively).
SEND0 State
P = 300ns HIGH
N = 150ns LOW
N = 125ns HIGH
SEND1 State
N=260ns LOW
P=130ns LOW
P=125ns HIGH
Should all be valid.
Going over the amount slightly does not violate the defined protocol in the PDF (real world may not be the same, ha).
Back of the envelope math (please correct me...long day)
Assuming 100% efficiency, that's 4,000K SPS (symbols per second). The only deterrent going over the 125ns/250ns signal speed is a reduction in bandwidth.
Looking from the response side...
REPORT_P and REPORT_N traffic is nothing. Sampling these at double the transition rate or 62ns is required.
If the PIC is running at 48MHz or 32MHz, we are still talking an order of magnitude+ faster than the ASICs SPS.
My educated guess is that Avalon's use of an FPGA has to do with features like direct Ethernet pool connection capabilities, web user interface, etc...