about UTMI_RXERROR_FAIL_COUNT bit

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

about UTMI_RXERROR_FAIL_COUNT bit

ソリューションへジャンプ
1,618件の閲覧回数
takayuki_ishii
Contributor V

Hello community, 

Our customer has an USB connection error.

In this time UTMI_RXERROR_FAIL_COUNT bit in USBPHYx_DEBUG0_STATUS register will be set.

To analyse this error, we hope some information about this counter bit.

Which error doe's it trigger the counter UTMI_RXERROR_FAIL_COUNT?

In Figure 66-1. USB 2.0 PHY Block Diagram, which module doe's generate UTMI_RXERROR status?

In customer products, i.MX6Q use as USB-peripheral.

And connect to Host CPU in their system.

Best regards,

Ishii.

ラベル(1)
0 件の賞賛
返信
1 解決策
1,482件の閲覧回数
gusarambula
NXP TechSupport
NXP TechSupport

Hello Takayuki Ishii,

The error is generated by the UTMI PHY module, marked as a UTMI microcell on the figure, with a dotted line.

 

Possible sources of receive errors are:

  • Bit stuff error has been detected during a FS receive operation
  • Elasticity Buffer overrun
  • Elasticity Buffer underrun
  • Loss of sync by the DLL
  • Alignment error, EOP not on a byte boundary
  • Vendor Specific errors

I hope this helps!

Regards,

元の投稿で解決策を見る

0 件の賞賛
返信
2 返答(返信)
1,483件の閲覧回数
gusarambula
NXP TechSupport
NXP TechSupport

Hello Takayuki Ishii,

The error is generated by the UTMI PHY module, marked as a UTMI microcell on the figure, with a dotted line.

 

Possible sources of receive errors are:

  • Bit stuff error has been detected during a FS receive operation
  • Elasticity Buffer overrun
  • Elasticity Buffer underrun
  • Loss of sync by the DLL
  • Alignment error, EOP not on a byte boundary
  • Vendor Specific errors

I hope this helps!

Regards,

0 件の賞賛
返信
1,482件の閲覧回数
takayuki_ishii
Contributor V

Hello Gusarambula,

Thank you for your response.

I will answer this information to my customer.

Best regards,

Ishii.

0 件の賞賛
返信