TUSB1210: Suddenly USB communication disconnection.

fangxing sun

Part Number: TUSB1210

Our project uses TUSB1210 as the ZYNQ 7000 extended USB port. At present, the USB communication is suddenly interrupted occasionally. The “URB-2” error log is displayed in the LOG.
I have the following three questions to help answer.
1. The official FAQ of ZYNQ 7000 mentions that the ULPI timing of TUSB1210 and ZYNQ 7000 do not match, but below two posts in the E2E forum have responded to this issue that TI has resolved in 2015. However, I noticed that the specifications of the latest version of the TUSB1210 have updated the timing parameters of the ULPI interface. What is the reason?

https://e2e.ti.com/support/interface/f/138/p/870247/3220928?tisearch=e2e-sitesearch

https://e2e.ti.com/support/interface/f/138/t/522352
2. Whether the latest ULPI timing of TUSB1210 can meet the requirements of ZYNQ 7000.

3. We tried to capture the waveform files before and after the problem with ULPI. I found that after URB-2 appeared, the signal of ULPI was abnormal. CLK always exists because of the output of ZYNQ7000. DIR and DATA2, DATA7 have occasional pulse waveforms. NXT, STP and other data have been low. Please help analyze what caused this situation. See the attached PPT file for the waveform.

over 5 years ago

0 fangxing sun over 5 years ago

Intellectual 310 points

Add ULPI waveform when URB-2 errorURB-2 ULPI error.pptx

0 Brian Zhou over 5 years ago in reply to fangxing sun

TI__Guru*** 145105 points

it seems the fix is only for Tdd delay time, but hold time is still not meet ZYNQ 7000 requirement.

0 fangxing sun over 5 years ago in reply to Brian Zhou

Intellectual 310 points

Dear Brian

Thanks for your quick response.

How about the No3 question, Do you have some ideas about this issue?

0 fangxing sun over 5 years ago in reply to Brian Zhou

Intellectual 310 points

Dear Brian

I have additional questions.

TI has two version specifications "H" and "I". Fix the Tdd delay time issue in "H" or "I" or both?

From "H" to "I" whether have silicon version change?

0 Brian Zhou over 5 years ago in reply to fangxing sun

TI__Guru*** 145105 points

From H to I, only change ULPI setup time.

From history , I didn't see changes for Tdd.

also Hold time is not meet ZYNQ 7000 spec.

0 fangxing sun over 5 years ago in reply to Brian Zhou

Intellectual 310 points

Dear Brian

Thanks for your quick feedback.

1. Why TI change ULPI setup time, because change silicon version or check design re-estimate or simulation again.

2. Change setup time is for optimizing or correct.

3.TI whether having the plan to optimize hold timing. If TI has, please tell me scheduled.

4. No.3 question please help analyze

0 fangxing sun over 5 years ago in reply to fangxing sun

Intellectual 310 points

Dear Brian

Do you have updated information?

0 Brian Zhou over 5 years ago in reply to fangxing sun

TI__Guru*** 145105 points

for setup time, we just correct it from max to min value.

for hold time, it was mentioned spec was changed from 0.2ns to 1.2ns, but I can never found any changes in any revision.

For q3, I sent waveform to designand see waht's wrong.

0 fangxing sun over 5 years ago in reply to Brian Zhou

Intellectual 310 points

Dear Brian

Thanks for your quick reply.

I still confuse how to check TUSB1210 hold time whether to meet Zynq-7000 requirement.

1. In Ver.H only check hold time minimum value is 0. TUSB1210 does not meet Zynq-7000 requirement.

2. In Ver.H hold time plus delay time minimum value is 0+1.2ns =1.2ns. TUSB1210 can meet Zynq-7000 requirement.

3. Because Ver.I delete delay time minimum value so hold time minimum still 0. TUSB1210 does not meet Zynq-7000 requirement.

Please help me confirm which calculation method is correct.

0 Brian Zhou over 5 years ago in reply to fangxing sun

TI__Guru*** 145105 points

sorry, my mistake.

for delay time, it was mentioned spec was changed from 0.2ns to 1.2ns, but I can never found any changes in any revision.

for hold time, it's always 0 on our datasheet

0 fangxing sun over 5 years ago in reply to Brian Zhou

Intellectual 310 points

Dear Brian

We still investigate this issue. We found TUSB_1210 power-on sequence has some problems. Old software version power-on reset low duration time is 15ms. New software version change reset time to 1ms. Please check the attached picture.

Could you help me confirm during TUSB1210 power on the mini reset low pulse width needed? If 15ms not enough, how many are suggested.

TUSB1210-RESET.pptx

0 Brian Zhou over 5 years ago in reply to fangxing sun

TI__Guru*** 145105 points

min reset time is 0.2us, so 1ms should enough.

Interface

Interface forum

TUSB1210: Suddenly USB communication disconnection.