• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 33 subscribers
  • Views 660 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TUSB2046B Errata

BertD
Prodigy 60 points
Other Parts Discussed in Thread: TUSB2046B, TUSB2077A

Hi,

 

we have several communication problems with a Bluetooth module connected via the TUSB2046B hub. We didn't have the problems before we used this hub.

I've read the Errata document (SLLZ051 - October 2006), and maybe the error described in this document has to do with our problem.

We are running Windows XP on the host machine. WinXP recognizes the hub perfectly and uses its class driver "usbhub.sys", called "Generic USB Hub". Reading the errata-document, I'm wondering the following question :

- How can I send the CLEAR_PORT_FEATURE(PORT_ENABLE) and RESET_PORT messages ?
Do I need to make changes to the usbhub.sys ? Do I need to write my own driver for this specific hub ?

 

Regards,

Cédrique

  • 0
    TI__Guru 60870 points

    Hi,

    Can you describe the communications problems you are seeing?  Does the device not appear at power up, or after a cable connection?  Or does the device lose connectivity?  Is the hub self-powered or bus-powered?  Is the bluetooth module on the same PCB as the hub?

    The errata you referenced is actually pretty uncommon and requires a driver modification to implement the workaround, there may be a simpler and easier to implement solution.

    Regards,

    Julie Nirchi

     

     

     

     

  • 0 in reply to JMMN
    Prodigy 60 points

    The devices loses connectivity. Sudden the Bluetooth software can't get info about the local module (application hangs) or gets totally wrong info (e.g. hardware manufacurer, hardware revision, ...)

    Also, other Bluetooth devices do find always the Bluetooth module, but often they show the module doesn't offer any services. This means, the module is working fine, but the services defined in software can't be transmitted because the communication between the module & software is gone.

    Restarting the Bluetooth software doesn't help then. After a reboot of the machine the problem is often gone. But we encounter the problem 1 time in 3 tries.

    We didn't change anything about the software. We just copy an installed image of the Windows OS.

    It never happens on devices were the Bluetooth module is directly connected to the host (without the hub).

     

    Regards,

    Cédrique

  • 0 in reply to JMMN
    Prodigy 60 points

    I forgot :

    • All devices are self-powered : hub & Bluetooth module.
      The hub is always powered. The Bluetooth module is powered off (by default) until Windows has fully booted (on desktop screen). Then we enable the Bluetooth power by setting a GPIO
    • When powering the Bluetooth module (via the GPIO), Windows always recognizes the module as it should (puts it in the Device Manager list)
    • The Bluetooth module is connected via a connector to the PCB. The cable we use is exactly the same one as on the machines without the hub.
  • 0 in reply to BertD
    TI__Guru 60870 points

    Hi,

    This doesn't sound like a hardware issue.  It sounds like the USB connection is being suspended.  You can check this pretty easily.  Once the bluetooth module drops off or loses connection, check to see if the SUSPEND output of the TUSB2046B is high.  USB automatically suspends after 3 ms of inactivity, the software may not be resuming the bus correctly.  Let me know if the bus is getting suspended and I can send additional information to determine why the system isn't resuming properly.

     

    Julie

  • 0 in reply to JMMN
    Prodigy 10 points

    Hi,

    I encountered a similar problem and still don't have an answer.

    I am using an ARM9 Marvell processor (WIN CE6 OS) and its downstream port is connected to a TUSB2077. Port 1 of the TUSB2077 is routed to a USB host connector. I connect an optical card reader to this port and some time the ARM processor doesn't receive data from the OCR, although my software tells me the port is still opened (I use a VCP driver).

    I then connect a 3rd party hub (self powered) to port1 of the TUSB2077 and the OCR to one of the external hub downstream port. The interesting fact is that everything starts working as soon I insert USB memory stick into the external hub . I can repeat this. Every time the OCR stops responding, I insert a USB stick and while USB stick is inserted, OCR works. As soon as USB stick is removed, OCR stops working after a while.

    This seems like a suspend problem. I cannot change the driver. Is there a way to stop the TUSB2077 suspending after 3mS?

    Riaan

     

  • 0 in reply to Riaan vdB
    TI__Genius 16430 points

    Riaan,

    USB Suspend is fully under the control of the host system.  The TUSB2077A (or any other hub peripheral) can only respond to commands issued by the hosts system, which is a combination of the host controller and operating system.