TNETE2201B: SYNC issue

ttd

Mastermind 8120 points

Part Number: TNETE2201B

Hi Nasser,

Could you answer that this event does not occur except for Autonego / C / code?

Following E2E is already locked, so I make a related question.

https://e2e.ti.com/support/interface-group/interface/f/interface-forum/977447/tnete2201b-sync-issue

Best Regards,

ttd

over 3 years ago

0 Nasser Mohammadi over 3 years ago

TI__Guru* 93670 points

Greetings,

I am checking into this and will let you know within the next 2 days.

Regards ,, Nasser

0 ttd over 3 years ago in reply to Nasser Mohammadi

Mastermind 8120 points

Hi Nasser,

I'm looking forward to your investigation.

Best Regards,

ttd

0 ttd over 3 years ago in reply to Nasser Mohammadi

Mastermind 8120 points

Hi Nasser,

Do you have any update so far?

Regards,

ttd

0 Nasser Mohammadi over 3 years ago in reply to ttd

TI__Guru* 93670 points

Hi,

I apologize for the delay. I should have comments by this coming Monday afternoon US time.

Regards ,, Nasser

0 Nasser Mohammadi over 3 years ago in reply to Nasser Mohammadi

TI__Guru* 93670 points

Greetings,

Based on discussions with other colleagues, this RBC stretching has not been observed or reported during our evaluation.

Regards ,, Nasser

0 ttd over 3 years ago in reply to Nasser Mohammadi

Mastermind 8120 points

Hi Nasser,

Thank you for your reply.

I understand that you don't have route cause for this RBC stretching issue.

Currently, when change LCKREFN such as high → low → high, a correct 62.5MHz clock was output and SYNC was also high.

Is it correct workaround?

Best Regards,

ttd

0 Nasser Mohammadi over 3 years ago in reply to ttd

TI__Guru* 93670 points

Greetings,

Yes this is a correct workaround. This is a reliable workaround that has worked every time.

Regards ,,Nasser

0 ttd over 3 years ago in reply to Nasser Mohammadi

Mastermind 8120 points

Hi Nasser,

Thank you for your reply.

I understand that workaround is correct.

It was confirmed that the extension of RBC0 was resolved and the communication was linkedwhen SYNCEN was pulsed.
According to the data sheet, it seems that SYNCEN has enabled / disabled the circuit that generates the SYNC signal after the PLL.
It recovers when toggling SYNCEN. Is this not just because the PLL is not pulling in the signal, but the sync detection circuit in the TNETE2201BPJW may not be working properly?

Best Regards,

ttd

0 Nasser Mohammadi over 3 years ago in reply to ttd

TI__Guru* 93670 points

Greetings,

Extension of the RBCO causes signal to drift with respect to the point where PLL was locked. PLL was not able to pull in the signal and therefor by pulsing the SYNCEN signal we restart the PLL and now is able to lock the signal after RBCO extension.

Regards ,, Nasser

Interface

Interface forum

TNETE2201B: SYNC issue