• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 32 subscribers
  • Views 656 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.

TSUB3410

Klaus Helmgens
Prodigy 50 points
Other Parts Discussed in Thread: TUSB3410

Dear Roberto,

I have a problem with the TUSB3410 too, but different. The funny part is that I had a problem on my former system (XP 32-Bit) too, but somehow I solved it with the help of Dr. Google - around 3 years ago. This time I can't find any solution. My system is Win 7 x64 Ultimate SP1 (all Updates as by today).

I am using an USB-2-Serial cable (came with a Huawei Terminal Adapter for CDMA) which gets identified as TUSB3410 Device (COM7). The driver is 6.7.2.0  from 03/20/2013...no problems during installing...

Now I want to use the cable (as I did before on XP as well) as a bridge between a MCU Device I build and Putty...

If I hook the MCU direct to the build in RS232-Port (COM1) on my PC - it works...if I use the TUSB3410 cable with the same setting (COM7) no data gets transmitted. I even tried all different setting (XON/XOFF etc. FIFO ON/OFF, Change of COM-Port to COM2...etc,etc,etc...) There is no data transfer...even I used another similar cable (I have around 40 of them here) - no transfer....

Unfortunately I sampled some of the TUSB3410 Chips last month and was about to integrate them in my MCU application...but if the customers later will face this kind of problems to connect/access - I have to reconsider....

I hope you can help me to find a solution, coz I don't want to mix within my MCU App...almost all components are TI...

Thx...

Dr. Klaus Helmgens  

  • 0
    TI__Genius 11255 points

    Hello Klaus,

    I have some questions about your problem. Can you verify that the pinout of the cable that you are using is the same as the standard COM port? Have you tried to perform the communication between two PCs instead of the MCU.

    Regards,

    Roberto

  • 0 in reply to Roberto Diaz
    Prodigy 50 points

    Hello Roberto,

    thx for the reply. I was using the same cable before under XP-x86. I had some problems there before too, but after 2 weeks of research with Dr. Google I found finally a third-party (Belkin) driver which worked. But now with win7-x64 I cant find any driver which will work. I remember that I was checking one of the cable by cutting it open and the internal hook-up was accordingly to the AN for a straight thru USB-2-RS232 converter cable...nothing special...

    I installed meanwhile "XP-Mode-32" for Win7-x64 but due to the fact that the hardware ports still gets managed by Win7-x64 it still wont work.

    Under Suse 13.1 I was able to get it running immediately - but I can't expect that my clients will run Linux - just to read out the data..

    When I see how many people have problems with TUSB3410, I wonder why TI is not able to solve the issue. If you just use Google - you will find thousands of people...do you have any explanation?

    As mentioned, the cable are from Terminal Adapters from Huawei and they are normal - not cross-over. If I hook up one of the terminals with another standard RS-232 cable to my internal COM-Port it works as well...

    I build a temp. monitor for laboratory and pharmacy fridges here in Ethiopia and the government will make it a must by law soon. We have the unique chance to be the first or maybe sole supplier for those monitoring devices, but we need to be able to provide a read-out function to the clients/government. They plan to send every year a team around to check the quality and in the same moment to read-out the monitoring devices. Our deadline for the prototype is 27th of November 2014....please help...as I said...I was planning to add the TUSB3410 direct to my device, but as long as even a standard cable wont work, I doubt that it will work if I implement the chip directly.

    Best regards

    Dr. Klaus Helmgens