This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
We are having trouble in debugging our new serdes circuity. After pulling BISTEN high, we got LOCK signal acting as a pulse with very short high time. Do you have any clues?
Going through spec of 954, 'During pin control BIST, the values on GPIO1 and GPIO0 pins will control whether the Serializer uses an external or internal clock for the BIST pattern. The values on GPIO1 and GPIO0 will be written to the Serializer register 0x14[2:1].'
Does it mean, 954 will sample GPIO0/1 of 954 and use them to decide 953's clock source?
Below is snapshots of our sch, please kindly help to review and provide your feedback.
Thank you and look forward to hearing from you as soon as possible.
Bgs/Sen
Hi Steven,
But problem is, our design and cables are based on STP mode. In STP mode, we can not even LOCK properly in BISTEN=H mode, which means there is no way to communication with 953(Processor can only access 954).
If we debug our board to coax mode, I2C is OK. But all in all, our design, our cables are STP mode, we don't want coax mode.
Any idea why we can not access 953 under STP mode?
Thank you!
Rgs/Sen