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.

RESET bit stuck (bit 5 of USB FUNC_CTRL register) in 65950

Other Parts Discussed in Thread: OMAP3503

I have a single unit where the RESET bit in the USB FUNC_CTRL register is stuck high and the OMAP isn't communicating with the attached USB device. I can warm/cold start the attached OMAP3503 but the RESET bit in the TPS stays high. I can unplug, replug the USB device with no change. I would like to understand what caused this to see if it can be prevented, but I would also like to know if there are a series of TPS register pokes I might try that would be able to correct this, or how I might get the 65950 to do the equivalent of a cold start.(I'm new to this chip and am still reading the TRM ;) I don't want to cycle power on the TPS just yet as I'm not sure I can recreate this problem. Our unit is a remote headless battery backed device so this kind of thing happening in the field would brick a unit. Currently I don't know how to effectively make the 65950 do the equivalent of a cold start (I'm new to this chip and am still reading the TRM ;) We have hundreds of hours on dozens of identical devices and to my knowledge we have only seen this problem twice. I've dumped all the USB registers and compared against units that are working.

Jeff

***** good_twl4030_usb.txt

00:04 => 45 

00:05 => 45 

00:06 => 45

***** BAD_TWL4030_USB.TXT

00:04 => 60

00:05 => 60

00:06 => 60

***** good_twl4030_usb.txt

00:09 => 18

00:0a => 26

00:0b => 26

00:0c => 26

00:0d => 1f

***** BAD_TWL4030_USB.TXT

00:09 => 18

00:0a => 24

00:0b => 24

00:0c => 24

00:0d => 1f

*****

 

***** good_twl4030_usb.txt

00:13 => 06

00:14 => 00

00:15 => 01

00:16 => 00

***** BAD_TWL4030_USB.TXT

00:13 => 06

00:14 => 0f

00:15 => 0c

00:16 => 00

*****

 

***** good_twl4030_usb.txt

00:8b => 00

00:8c => a2

00:8d => 00

***** BAD_TWL4030_USB.TXT

00:8b => 00

00:8c => 82

00:8d => 00

*****

 

***** good_twl4030_usb.txt

00:fb => 00

00:fc => 26

00:fd => 00

00:fe => 06

00:ff => 01

***** BAD_TWL4030_USB.TXT

00:fb => 00

00:fc => 20

00:fd => 00

00:fe => 07

00:ff => 01

*****

 

 

 

 

 

  • Hi,

    If you are stuck in such a bad state then you cannot really do anything. I have not heard this happen on any platform before. I know of a similar issue that came across long time back. That was also an extremely low probability problem.

    Are you trying to use some resets on OMAP that cause these issues?

    The problem I am trying to recollect was something to do with the way reset was done on OMAP. If it is something similar then I can try to give you the software fix. your problem may be different. But, again this is such a low probability issue that I am not sure if you can try to replicate it after the fix.

    Let me know some more details on the reset and I will try to dig to find what we did then.

     

    Regards,

    Gandhar.

     

  • Hi Gundar,

    Perhaps this does have something to do with how were are resetting the OMAP. We are running repeated OMAP resets on a few of our units and the problem

    is identified (can't connect to USB device) shortly after reboot. Previous to the reboot the USB device was connected and working. I would appreciate if you

    could find the software fix to which you referred. We had a second failure occur on a second unit today, so currently we have two units with the failure

    (RESET stuck high) latched. I'm able to interactively set registers on the TPS on the latched failed units if your fix involves that chip. What additional kind of

    info can I provide on the OMAP resets?

     

    thanks,

    Jeff