e-link polarity settings: do not work for RD53B CROCv1 SCC
We need to use the latest Ph2_ACF software/firmware to test the new e-link polarity settings. However, the latest Ph2_ACF software/firmware is not working for our RD53B SCC setup. We are using a port card (lpGBT-v1), a RD53B CROCv1 SCC, a display board (CP) cable, an adapter board (with jumpers for e-link polarity), and a Type 5K e-link (15 to 45 pin) inserted into port card slot J4.
Ph2_ACF v4-13, FC7 FW v4.5 for RD53B CROCv1 SCC, port card slot J4: this configuration is working
- Important note: The HLS settings (RxHSLPolarity and TxHSLPolarity) are used (incorrectly) for e-link polarity in Ph2_ACF v4-13! The optical link polarity is not configurable in Ph2_ACF v4-13.
- HLS settings: RxHSLPolarity="0” TxHSLPolarity="0"
- E-link settings: Id="15" Lane="0” RxGroups="2" RxChannels="0" TxGroups="3" TxChannels="2"
Ph2_ACF v4-18, FC7 FW v4.8 for RD53B CROCv1 SCC, port card slot J4: this configuration does not work
- We can communicate with the port card, but not with the RD53B chip.
- Optical link settings: RxHSLPolarity="0” TxHSLPolarity="0”
- We tried all four combinations; only this combination results in communication with the lpGBT.
- E-link settings: Id="15" Lane="0” RxGroups="2" RxChannels="0" RxPolarities="0" TxGroups="3" TxChannels="2" TxPolarities="0”
- Communication is not working with the RD53B chip; we have tried all four combinations of RxPolarities = [“0”, “1”] and TxPolarities = [“0”, “1”].
- The setting TxPolarities="0" results in the expected RD53B chip current, while the setting TxPolarities="1" does not; thus, TxPolarities="0" is likely correct.
- What we have tried: Ph2_ACF v4-18 and CMS IT master branch, two Type 5K e-links, all jumper settings (e-link polarity), all e-link polarity software settings, and all optical link polarity software settings.