This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM3730 <--> USB3320 ULPI <---> LAN9514i USB-Hub+Ethernet Temperature Problem below -22°C

Other Parts Discussed in Thread: DM3730, TUSB1210

Hi,

we're using the DM3730 (at HSUSB2 ULPI-Interface) with SMSC USB3320 ULPI and LAN9514i USB-Hub with Ethernet (LAN9514 like on the BeagleBoard xM). All components are on-board and are in the extended temperature range. The system clock is 26 MHz.

All works fine for high environmental temperatures (> 60 °C) and down to approx. -22°C. Below that temperature, the onboard hub doesn't gets enumerated correctly and the USB doesn't work. Typical error messages are as shown below and have been confirmed many times with different devices. The error messages change with temperature. At temperatures below -34°C it seems that the USB hub does not get detected at all.

....
Starting system message bus: [   19.085205] ehci-omap ehci-omap.0: port 2 reset error -110
[   19.090728] hub 2-0:1.0: hub_port_status failed (err = -32)
dbus.
Starting udev
[   19.311798] ehci-omap ehci-omap.0: port 2 reset error -110
[   19.317321] hub 2-0:1.0: hub_port_status failed (err = -32)
[   19.671142] ehci-omap ehci-omap.0: port 2 reset error -110
[   19.676666] hub 2-0:1.0: hub_port_status failed (err = -32)
[   20.147857] ehci-omap ehci-omap.0: port 2 reset error -110
[   20.153411] hub 2-0:1.0: hub_port_status failed (err = -32)
[   20.238922] clock: Could not find divisor for target rate 0 for clock dpll4_m5_ck parent dpll4_ck
[   20.255157] hub 2-0:1.0: Cannot enable port 2.  Maybe the USB cable is bad?
[   20.263732] omap3isp omap3isp: clk_set_rate for dpll4_m5_ck failed
[   20.327209] ehci-omap ehci-omap.0: port 2 reset error -110
[   20.333007] hub 2-0:1.0: hub_port_status failed (err = -32)
[   20.546020] ehci-omap ehci-omap.0: port 2 reset error -110
[   20.551544] hub 2-0:1.0: hub_port_status failed (err = -32)
[   20.764801] ehci-omap ehci-omap.0: port 2 reset error -110
[   20.770324] hub 2-0:1.0: hub_port_status failed (err = -32)
[   20.983551] ehci-omap ehci-omap.0: port 2 reset error -110
[   20.989288] hub 2-0:1.0: hub_port_status failed (err = -32)
[   21.202270] ehci-omap ehci-omap.0: port 2 reset error -110
[   21.207794] hub 2-0:1.0: hub_port_status failed (err = -32)
[   21.213409] hub 2-0:1.0: Cannot enable port 2.  Maybe the USB cable is bad?
[   21.220428] hub 2-0:1.0: unable to enumerate USB device on port 2

  • Is there a known issue with DM3730 and USB 3320 at low temperatures?
  • Is this problem related to the DPLL5-Problem discussed in the DM3730 errata: "Advisory 2.1 USB Host Clock Drift Causes USB Spec Non-compliance in Certain Configurations"?
  • We're wondering abount exchanging the USB3320 with an TUSB1210. Does that make sense?

Thanks and BR Roland

 

  • Hi Roland,

    This problem seems like hardware issue. The problem should be due to only one component failure or if it is a passive component its parameters may be changed. I recommend you to test all components on the board which are related to the USB. What is their behaviour in this temperature. You could try to exchange the USB3320 with TUSB1210 and verify the system.

    BR

    Tsvetolin Shulev

  • Hi Tsvetolin,

    thanks.

    We replaced the USB3320 with the TUSB1210: We reached -31°C as the lowest temperature USB was working, however we had 1 or 2 times the same result (-31°C) also with the USB3320. We need to achieve around -35°C.

    So the problem is not solved yet. It has been verified that all components are in the industrial temperature range.

    Do you think the DM3730 DPLL5 Problem at 26 MHz (pls refer to Ti SPRZ319e Advisory 2.1, DPLL5 setting) could cause the described USB malfunction at low temperatures? Up to now we could not apply the patch to our Kernel 2.32.

    Any other ideas?

    BR Roland

     

  • Hi Roland,

    The errata described in Advisory 2.1 - 'USB Host Clock Drift Causes USB Spec Non-compliance in Certain Configurations' is not related to the temperature range conditions. But you should check the settings in the Table 36. DPLL5 Configurations With 13 MHz and 26 MHz Clock Frequencies.

    The problem is hard to debugging and I recommend to test the specification of all components related to the USB not according their data sheets but in relevant temperature conditions.

    BR

    Tsvetolin Shulev