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.

OTG Host Babble Issue

Hi,

I am using TPS 65930 PMIC and AM 3730 processor.I am facing problem in OTG host mode for USB flash drive during BOOT. But during plug-in cases it is working well.One different i tracked is during boot i am getting correct  INTRUSB (0x10)  and DEVCTL value is 0X3D(0011 1101) .Due this when i try to establish the host mode connection during boot i got babble condition.


But in working case ie insertion i am getting  INTRUSB (0x10)  and DEVCTL value is 0X5D(0101 1101) .

 

From this i am suspecting that  DEVCTL reg 6th and 5 th bit value may be invalid during boot up case.

My questions are

1.Is USB flash drive High speed device?

2.If yes for Q1,then why i am getting invalid DEVCTL reg value during boot? 

3.If yes for Q1 ,Any way to recover from this invalid DEVCTL reg value during boot? 

4.Are Keyboard and mouse low speed devices?

Note:

My OS platform is Wince6.0.I asked the question here.But not get any response till now. Since this is some what  general question i am asking it here. Apologies if this is wrong forum.   

  • Hi,
     
    How can anyone say what speed your devices are (or keyboard or mouse)? This depends entirely on the device. You should search for the device model/manufacturer and see its specifications from their site.
  • Thanks.

    From the spec i found USB flash drive is Hi-Speed USB 2.0.But my question is during boot i am getting DEVCTRL 0x3d. It seems that my device is detected as low speed device.I am thinking that this may be the reason why i am getting babble condition when i try to establish host connection when this DEVCTRLvalue. Am i going in  right path to debug this babble condition or some other reason caused this babble interrupt(INTRUSB 0x04) ?

  • It's possible the signal integrity of the interface itself is poor which could cause both babble events and the failure of HighSpeed capable devices from enumerating at HighSpeed. 

    Do all HighSpeed devices fail in this same manner?

  • Gopinath S said:
    From the spec i found USB flash drive is Hi-Speed USB 2.0.But my question is during boot i am getting DEVCTRL 0x3d. It seems that my device is detected as low speed device.

    You can check if your device is high-speed or not by plugging it into a PC.

    Your question why devctl is 0x3d is really for WinCE, since this forum does not provide WinCE support, so we cannot answer this question from sw perspective.

    But one thing you can quickly check is to ensure POWER[SOFTCONN] and/or DEVCTL[SESSION] bit should not be set too early until your MUSB driver is fully initialized. MUSB starts to detect the device only when these two bits are set.

  • -DK- said:

    Do all HighSpeed devices fail in this same manner?

    Yes.All the high speed device as well as full speed device fails in similar manner during boot up.But working well during plug-in cases.

    But low speed device is working well in both the cases.

  • Hi,

    One more thing i analysed with this issue.

    When HS and FS device failed during boot,i found the DEGUG regigter value is 0x11(0001 0001).

    But the same register holds the value of 0x10(0001 0000) during working condition(For LS devices). So my question what does these least two significant bits means?

     i am not able to under stand from the data sheet since it seems more hardware specific.

    Also i found one more register which is conflicts between Not working HS device and Working LS speed device.

    ie.OTHER_INT_STS register.It holds value of 82H(1000 0010)when booted working LS device and holds value of 22H (0010 0010) when booted with HS device.

    what does the 5th bit indicates here?

  • Hi,

    Any updates on this please?

  • I am not sure what document you referred about those two registers. I am not aware of it. But from the doc screenshot you posted, DEBUG[1:0] is the state of DP/DM lines, which changes most of the time. So I would think those two bits are not related to the babble issue.

  • Hi,

    Thanks.Just for information I have used this(TPS65930) documents to refer those registers.