Unanticipated USB disconnection for i.MX6 Solo

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Unanticipated USB disconnection for i.MX6 Solo

1,178 Views
yuuki
Senior Contributor II

Dear all,

Our system has a problem of the unanticipated USB disconnection.

I found following Errata.

http://cache.nxp.com/files/32bit/doc/errata/IMX6SDLCE.pdf

- ERR004534 USB: Wrong HS disconnectio n may be generated after resume

- ERR004535 USB: USB suspend and resume flow clarifications

Our system is based on L3.0.35_4.1.0_130816_source.tar.gz(NXP BSP).

I understand that these Workarounds are included in this BSP.

However, I suspect that Errata issue occurs.

Therefore I want to confirm whether these Workarounds are included.

Would you tell me a file position and the concrete code that these Workarounds are included in?

Best Regards,

Yuuki

Labels (2)
0 Kudos
5 Replies

662 Views
vladimirpopov
Contributor I

Hello,

according to the ResolvedDefects.html document from BSP L3.0.35_4.1.0, these problems seem to be addressed by next fixes:

  • ENGR00218789 USB disconnect after suspend/resume #relates to i.MX6Q processor only
  • ENGR00221317 USB work abnormally after suspend/resume #it looks like it has been reverted by ENGR00225131
  • ENGR00221716 Mx6 Some highspeed device remote wake up fail
0 Kudos

662 Views
CarlosCasillas
NXP Employee
NXP Employee

Hi Yuuki,

We are internally discussing your case. In the meantime, could you please share why do you suspect that the errata is still present? Do you have any reproducible procedure for test it?

Hope this will be useful for you.

Best regards!

/Carlos

0 Kudos

662 Views
vladimirpopov
Contributor I

Hello Carlos,

We also experience this problem. Please find a quote from dmesg log below. Our build is based on one of Lollipop versions of BSP.

P.S. We have a procedure for reproducing this problem. It requires sending UDP packets with a specific interval (5-20 s) to our device (the USB HS device is a 3G modem). After some time, it triggers the problem.

<7>[16942.565316] PM: Finishing wakeup.
<4>[16942.565336] Restarting tasks ...
<7>[16942.565472] ci_hdrc ci_hdrc.0: at ci_runtime_suspend
<7>[16942.565771] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
<7>[16942.565928] hub 1-0:1.0: port 1, status 0513, change 0000, 480 Mb/s
<6>[16942.566005] usb 1-1: USB disconnect, device number 5
<7>[16942.566059] usb 1-1: unregistering device
<7>[16942.566086] usb 1-1: unregistering interface 1-1:1.0
<4>[16942.571726] done.
<6>[16942.572027] PM: suspend exit 2017-01-19 05:46:29.516765335 UTC
<6>[16942.573945] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
<6>[16942.575941] option 1-1:1.0: device disconnected
<7>[16942.576588] usb 1-1: unregistering interface 1-1:1.1
<6>[16942.577654] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
<6>[16942.580011] option 1-1:1.1: device disconnected
<7>[16942.580791] usb 1-1: unregistering interface 1-1:1.2
<6>[16942.582188] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
<6>[16942.582979] option 1-1:1.2: device disconnected
<7>[16942.584381] usb 1-1: unregistering interface 1-1:1.3
<6>[16942.587836] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
<6>[16942.588925] option 1-1:1.3: device disconnected
<7>[16942.590449] usb 1-1: unregistering interface 1-1:1.4
<7>[16942.591362] usb 1-1: usb_disable_device nuking all URBs
<3>[16942.693745] ci_hdrc ci_hdrc.1: port 1 reset error -110
<7>[16942.693903] hub 1-0:1.0: port 1 not reset yet, waiting 50ms
<7>[16942.752602] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
<7>[16942.962650] hub 1-0:1.0: port 1 not reset yet, waiting 200ms

0 Kudos

662 Views
yuuki
Senior Contributor II

Dear Carlos-san,

Thank you for your support.

We do not understand a reproduction procedure because problem reproduction is very rare.

We suspect it like that from log.

Please see USB disconnect log.txt.

Best Regards,

Yuuki

0 Kudos

662 Views
CarlosCasillas
NXP Employee
NXP Employee

Hi Yuuki,

Unfortunately, L3.0.35 BSP is no longer supported. Besides, it is also difficult to determinate if it is still present or not because it could not be reproduced with a determined procedure. So, do you have the chance of testing if this behavior is also present with a newer BSP version? L4.1.15 is now available.

Hope this will be useful for you.

Best regards!

/Carlos

0 Kudos