• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 32 subscribers
  • Views 472 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.

Using Multiple TUSB3410 Devices on Single PC

paddu
Intellectual 915 points
Other Parts Discussed in Thread: TUSB3410

Hi,

Our customer is using TUSB3410 in their custom board 

and in their mass production test process they are connecting two

TUSB3410 board one as a jig to test the target boards and the other the target TUSB3410.

Both have different descriptors.

 

And they are removing the target devices with the below sequence.

1.Close the Com port

2. Remove D+,D- after 200ms

3. Remove VBUS(external power supply) after 50msec

 

Around once in 50 time there are having the trouble with 

the com port, the device manager shows yellow mark on the TUSB3410 com port

and they cannot continue with the next device because the COM port 

doesn't open untill they remove the USB cable of the "TUSB3410 board used as a jig to test".

 

Is there any reason for the yellow mark on the TUSB3410 com port.

This yellow mark is occurs when they remove one TUSB and another TUSB remains

connected to the PC.

 

Regards.

 

  • 0
    TI__Genius 11255 points

    Hello Paddu.

     

                    I just want to know more details about the issue scenario in order to reproduce it at our end.

     

                    What is the driver version are they using? Also I want to know if they are trying a custom Firmware or it’s our standard FW (included in the driver installer package). And finally what is the Operating system that they are using?

     

    Regards,

    Roberto.

  • 0 in reply to Roberto Diaz
    Intellectual 915 points

     

    Hello Roberto,

     

    Thankyou so much for considering this issue.

    Actuall our customer has stopped production for a while because of this error.

     

    This situation has occured in the mass production site and 

    below the block diagram is their present test process.

    And as mentioned above they are using switches and delay in their test setup to create a closing sequence as below .

     

    1. Close the Com port

    2. Remove D+,D- after 200ms

    3. Remove VBUS(external power supply) after 50msec

     

     

    They are using the latest version of the drivers provided from TI

    and the firmware is Standard one.

    They are using HP compaq PC with Windows XP SP3.  

     

    I think you can reproduce this by plugging and unplugging (around 50 times)

    two TUSB enbled target bords(TI's EVM)

    one with standard PID and the other with a different PID.

     

    Today morning when I tried with two TUSB boards with different PIDS,

    there was a situation when I Pluggled/Unplugged both simultaneously my PC's

    USB port went wrong and I had to restart the PC.

     

    For time lets forget about this issue

    I would like to know whether the "yellow mark"  issue could be solved 

    if our customer uses different PID even with the end product (with TUSB) used as a tester

    shown in the above diagram.

     

    Regards.

     

  • 0 in reply to paddu
    TI__Genius 11255 points

    Hello Paddu,

     

                    As additional information I want to know the PID that they are using. It’s always the same PID or they have the issue with different PIDs?

     

                    The yellow bang can be caused if they are using an invalid PID.

     

    Regards,

    Roberto.

  • 0 in reply to Roberto Diaz
    TI__Genius 16440 points

    Also, are they serializing the units with individual serial numbers - this is addressed in our VCP implementation guide.

  • 0 in reply to DHarmon
    Intellectual 915 points

    Many thanks for the replies.

    And I am sorry for the delay,

    Since they are using separate EEPROM I believe they are using different PIDs with individual serial numbers.

    I will confirm it once again and let know.

    Meanwhile the "USB error code" on the device manager seems to be "43".

    Regards.