USB hang on error code -71

[kevincheng]

Hi community,

I have a strange question about i.MX6Q Android BSP (jb4.3_1.1.1).

We play Analog TV from usb dongle. Normally, just play video and audio, system is stable. But when we enable close caption, dmesg will show error code -32 each 1~2 mins , like the follow message,

[  494.953855] &0_-32&1_-32&2_-32&3_-32&4_-32cx231xx_vbi_clear_halt
[  494.987801] cx231xx_vbi_clear_halt all stop
[  494.999201] usb_clear_halt
[  540.821002] &3_-32&4_-32&0_-32&1_-32&2_-32cx231xx_vbi_clear_halt
[  540.843602] cx231xx_vbi_clear_halt all stop
[  540.853163] usb_clear_halt

about 30 mins, video, audio and close caption are stop. dmesg display huge error code -71 .

[  261.280238] cx231xxurb completition error -71.
[  261.289237] cx231xxurb completition error -71.
[  261.297863] cx231xxurb completition error -71.
[  261.306988] cx231xxurb completition error -71.
[  261.315988] cx231xxurb completition error -71.
[  261.325112] cx231xxurb completition error -71.
[  261.334238] cx231xxurb completition error -71.
[  261.343363] cx231xxurb completition error -71.
[  261.352363] cx231xxurb completition error -71.

We porting our BSP to EVB-sabresd. Same test behavior, and it will happen error code -32 each 1 hours, error code happen time become longer. And 10 hours happen error code -71, it seems have something different.

We check usb bandwidth by dd with usb storage,

in EVB, USB host bandwidth 21MB/s

             USB OTG Bandwidth 24MB/s

in our board, USB host bandwidth 19MB/s

             USB OTG Bandwidth 25MB/s

We test on USB host and USB OTG, there have the same result, it seems not the problem on bandwidth.

Otherwise, we observed some time happen error, there have some message like FB VSync error. So we try to remove hwcomposer_viv.imx6.so to hwcomposer_viv.imx6.so.org. When we do the same test, we found error code -32 happen on each 5mins and error code -71 happen on over 1.5 hours. It is so strange, why hwcomposer will effect the USB behavior. Have any ideal?  Thanks!!

[CarlosCasillas]

Hi,

Have you added the proper USB driver for TV dongles? Have you consider using a newer Android BSP?

I have internally discussed your issue; in case that having additional inputs, I will send you a reply.

Best regards!

/Carlos

[kevincheng]

Hi carlos,

We ask TV dongle company to build the USB driver by our kernel configuration, I think driver is no problem. On new BSP, our customer already mass production and every software are base on this kernel. We warrior about that have side effects on whole system, so not choice the new BSP.   Thanks!!

Regards,

Kevin

[CarlosCasillas]

Hi Kevin,

According with AE team, the device driver could not be ruled out.  A -71 error is a generic USB communications error.  Simply an URB was received the USB system could not understand or act upon.

usb_clear_halt is not a real error. It is just informational that the system has cleared any halt status on an endpoint.

So, is there any recreation scenario you could share that would reveal these errors for us?

Finally, the previous update recommendation is because JB4.3 is not supported anymore. Do you have any Sales/FAE assigned to this project?

Hope this will be useful for you. I will be waiting for your reply.

Best regards!

/Carlos

[kevincheng]

Hi Carlos,

When "-71" happen, we get the less message from system. You can look the kernel dmesg and logcat from follow link.

https://drive.google.com/file/d/0B6wokCK_hdHTUVVnR1FsY21nbHM/view?usp=sharing

https://drive.google.com/file/d/0B6wokCK_hdHTalhXOFVBSl9yVjQ/view?usp=sharing

Have any comment to get more infomation to debug?

For the last question, you mean is our FAE/salse or others ?

Regards,

Kevin

[kevincheng]

Hi Carlos,

We co-work with IC vendor WTMEC FAE Marco and NXP FAE Bruce Tsai.

Regards,

Kevin

[CarlosCasillas]

Hi Kevin,

According with AE team:

As mentioned a -71 is a generic USB communications error.

Another option could be using a USB analyzer on the system and see what is generating the error and trace the USB traffic. Before doing that you can run lsusb and see how the device has been identified.

The way USB works, in Linux, is the USB core negotiates with the device via URBs using some known commands. The flow is like:

- Sense plug in event

- Interrogate USB port for device ID

- Match ID to a device driver

- Start transferring data

Googling cx231 reveals it as possibly an audio or video capture device using the USB bus. If this is an integral part of their product the suggestion is analyzing the USB stream in order to correct the defect. The guess is that there is a problem with the cx231xx driver or there is too much noise on the USB port.

Hope this will be useful for you.
Best regards!
/Carlos
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[kevincheng]

Hi Carlos,

About your suggection. We have try to disable all device on USB port beside USB TV, but the result is same. Have any way to avoid noise or figure out what's noise on USB port?

Regards,

Kevin

[CarlosCasillas]

Hi,

The option could be a scope or an analyzer to obtain the eye diagram, in order to verify the signal integrity.

Hope this will be useful for you.

Best regards!

/Carlos

[CarlosCasillas]

Hi,

Regarding the last question, we are asking if you have any Sales Person or Field Applications Engineer from NXP, and, in case that yes, who is he/she?

I will send you an update ASAP.

Best regards!

/Carlos