Module configuration
In general, QA/QC confugurations can be used directly even in a FELIX/Optoboard setup. However, fer minor modifications are needed.
Speed
FELIX elinks are supposed to operate at 1.28 Gb/s. This is not always the case in QA/QC.
"CdrClkSel": 0
Pre-emphasis
When using 1.28 Gb/s in a Trenz/Ohio setup, pre-emphasis must be enabled. In a setup with the optoboard, pre-emphasis is not needed when cables are short.
"CmlBias0": 800
"CmlBias1": 0
"SerEnTap": 0
"SerInvTap": 0
Active lanes
For the moment, we always operate modules with just one active lane per chip.
"AuroraActiveLanes": 1
Output path
Depending on the exact combination of flex, cable and adapter boards, it can be a bit tricky to identify the right chip output to use. A trick that can simplify your life at the beginning is to enable all serializer outputs and use the output mux to copy the first aurora lane to all outputs. In this way you will get an output in any case (or even more than one if you have more than one link connected to the optoboard).
"DataMergeOutMux0": 0
"DataMergeOutMux1": 0
"DataMergeOutMux2": 0
"DataMergeOutMux3": 0
"SerEnLane": 15
"SerSelOut0": 1
"SerSelOut1": 1
"SerSelOut2": 1
"SerSelOut3": 1
Suppress service records and ID check
YARR cannot read register values for the moment, so features requiring register access must be disabled.
"ServiceBlockEn": 0
"EnforceNameIdCheck": false
Connectivity
In theory, the only modification needed to the connectivity is is to put the correct TX and RX link identifier. The indentifier to use are in the formt
ID = 64 * LinkId + eLinkId
eLinkId = 0, 4, 8, 12, 16, 20 (six elinks per link). For down-links eLinkId = 0, 2, 4, 6, 8, 10, 12, 14 (8 elinks per link).
The LinkId and eLinkId can be determined looking at the connectivity maps of the individual data path components or at the collective maps for specific configurations (see the "Module connections" section).