Solved - No Com Port? - TIAO Community

This site is best viewed in a modern browser with JavaScript enabled.

Solved - No Com Port?

pcfr33k

I just recieved my new TUMP Today. The drivers where already installed for the defective unit but when I plug this new one the Com port does not show up in Device manager. If I add it as legacy hardware it shows up as com3 with an explanation point by it.
Under USB Serial Bus Controllers I see all three components:
TIAO USB Multi-protocol Adapter A
TIAO USB Multi-protocol Adapter B
USB Composite Device.
Do I need to completly remove the TIAO drivers from the system and registry so when I connect the TIAO it will not automatically install them so I can re-install them or what else can I do to get this com port to show up which wil assign the port in order to use putty, terminal etc.
How do I completly remove the drivers? Advice on a fix please.
Thanks
EDITED:
This has now become a serious matter and I have lost all patience!!!!!
Both boards arrived Saturday with of them them a bent pin.
I cannot get either one to create a com port when connected.
Tired tow different laptops same results. One windows 7 64 bit and the other Windows 7 32 bit same results.
I have a feeling I was sent to bad TIAO!!!!!
EDITED AGAIN:
I have verified there is not one single thing wrong with my Laptops nor hardware. I just tried to USB/TTL adapters and as soon as I plugged them in the Prolific USB to Serial Comm Port was assigned in this case Com3.
Loopback between Rx/Tx works fine on these other pieces of hardware I tested!!
Something is wrong with both TIAO's sent out to me and this is making me very upset!!

TheOne

Hi, please use FT clean/CDM Uninstaller to clean all the FT drivers and reinstall latest TUMPA driver.
Here is the link to CDM Uninstaller:
http://www.ftdichip.com/Support/Utilities/CDMUninstaller_v1.4.zip
Select to uninstall all 0403 drivers.
Then reboot your machine.
You can download latest tiao tumpa driver from here:
http://www.tiaowiki.com/download//file.php?id=33
Unzip to a folder such as c:/temp/tumpa
After your machine is rebooted, plug the board to your pc, then follow the on screen menu to install the latest tumpa you just unzipped to c:/temp/tumpa
Thanks

pcfr33k

CDM Uninstaller GUI shows Vednor ID 0403 and Product ID 6001. I click add because nothing is in the Big sqaure field then highlight then remove devices at the bottom.
Removed fail:
Failed to remove Device VID_0403 PID_6001. The device could not be found on the system.
The other uninstraller command window shows invalid argument when I run that one.
I replied again to the open ticket and attached th log.
EDITED:
The application defaults to those values so looked up the IDs in the device manager.
The VID is correct 0403 but the PID is actually 8A98 so I put that in instead and it removed it. Rebooted and followed the rest of the instructions and for some reason the "USB Composite Device" continues to install on its own as soon as I plug in the TIAO TUMPA.
Is this the problem? Is this one preventing the USB to Serial COM to show up in the device manager or is there actually a hardware issue with both these TUMPA's?
At this point I think you need to "go to meeting" or some way of sharing the desktop so you can see exactly what is going on.

xyz123

I think Port A and Port B require different drivers. Port A - this is where JTAG control is done. Port B - COM port. I did not care for COM on mine so I did not do it. I do not know where to get COM port driver though.

pcfr33k

Mike,
I have updated my ticket. I made a fresh install of windows 7 32 bit. I followed the step by step instructions online. The "OTHER DEVICES" USB to Serial Port never show up in device manager.
My first response in my ticket was a bent pin on one of the TUMPA's. Either they were damaged from shipping or just defective.
YOu can view my ticket but it looks like I need to RMA these 2 units.
My original unit had no issues installing the drivers and the USB to serial did show up on the original device.
So what is wrong with these devices why is the USB to serial Port not showing up?
Thanks

pcfr33k

Mike wrote: Hi, please use FT clean/CDM Uninstaller to clean all the FT drivers and reinstall latest TUMPA driver.
Here is the link to CDM Uninstaller:
http://www.ftdichip.com/Support/Utilities/CDMUninstaller_v1.4.zip
Select to uninstall all 0403 drivers.
Then reboot your machine.
You can download latest tiao tumpa driver from here:
http://www.tiaowiki.com/download//file.php?id=33
Unzip to a folder such as c:/temp/tumpa
After your machine is rebooted, plug the board to your pc, then follow the on screen menu to install the latest tumpa you just unzipped to c:/temp/tumpa
Thanks

Mike or whoever is responsible to help me figure out what is going on. SInce your last post I have not heard back from anyone here or anyone from DIYGADGET support ticket? I made a new ticket.
If I don't get this resolved I have to return these items ASAP!!

[deleted]

It is possible that some of your system files are corrupt, or your PC's USB chip has hardware problem.
Please try your TUMPA in another PC,

pcfr33k

I did try in another PC. I also did a fresh install of windows. And like I said I have tried all my other serial to USB hardware on both PC and they bring up the COm port and assign a port number.
It has to be the TUMPA hardware!!

EagleG

I have just received my board today and I have exactly the same problem, ie Adaptor A and B plus two composite USB devices but no Comm Port.
Also running Windows 7 64bit.

[deleted]

Are you using the latest version of the driver?

EagleG

I am using the latest driver, the installation goes as described in your document.
I removed all old drivers and rebooted as suggested.
I use a number of FTDI devices, all of which work on the same machine.
Is there any way I can check the software version in your board?

pcfr33k

Its starting to sound like something is wrong with the bootloader or firmware on this batch. I am getting another 2 in the mail next week if I encounter the same problem Im done with trying to get this to work.
I think you guys need to check this latest batch of TUMPA's your shipping out!!!
Can you please look over the units I sent back please. I believe I made note for Mike to look it over. Who knows maybe something went wrong in the bootloader firmware upload at factory?
Is it possible a bad batch of FTDI chips all of a sudden? Most people use the TUMPA for jtag so who knows maybe just a bad batch or something wrong with the program that compiled the firmware?
This is the second person to report this!!!
If I cannot get the new ones to work I will RMA them and just use the Bus Pirate I guess!!

TheOne

Hi, this is caused by the EEPROM configuration. The port B's driver is configured to D2XX direct, thus you don't see virtual COM port in your device manager.
The driver for port B can be changed to virtual COM port by FT_Prog. Please follow the following instructions to add COM port:
http://www.tiaowiki.com/w/How_to_enable_virtual_COM_port_on_TUMPA
The template file we used to flash the eeprom has not changed since day one (set virtual COM port for port B), we don't know why it was changed to D2XX during flash. We are investigating it.
Sorry for any inconvenience.

TheOne

OK, found the problem.
FTDI's recently change to FT_Prog.exe caused the problem.
We used to use the following element in our template to config the virtual port:

<VirtualCOM>true</VirtualCOM>

Which worked fine on previous versions of FT_Prog, however starting from v2.6.8.0 of the FT_Prog the above element was changed to:

<VCP>true</VCP>

FT_Prog doesn't throw any exception when we load our current template.
We have changed our template to use the new element, so all new orders should not have any problem.
Again sorry for the inconvenience.
-Mike

EagleG

Thank you, everything working OK now

TheOne

EagleG wrote: Thank you, everything working OK now

Thank you

pcfr33k

Mike wrote: OK, found the problem.
FTDI's recently change to FT_Prog.exe caused the problem.
We used to use the following element in our template to config the virtual port:
<VirtualCOM>true</VirtualCOM>
Which worked fine on previous versions of FT_Prog, however starting from v2.6.8.0 of the FT_Prog the above element was changed to:
<VCP>true</VCP>
FT_Prog doesn't throw any exception when we load our current template.
We have changed our template to use the new element, so all new orders should not have any problem.
Again sorry for the inconvenience.
-Mike

Mike 2 TUMPA's where shipped out Thursday last week, will this have the update?
Its been a real mess for me as far as returning and shipping costs!!!!
Did you get a chance to look at my initial returned item where the FTDI chip was getting hot and stopped working.
Thanks
EDITED:
Will FT_Prog will actually burn into the firmware and do you think I will still need to do this on my last order?
DIYGADGET.COM: Shipment # 231210057516 for Order # 201210032193

TheOne

pcfr33k wrote: Mike 2 TUMPA's where shipped out Thursday last week, will this have the update?

Unfortunately no. The new orders ships out today will have the update.

pcfr33k wrote: Its been a real mess for me as far as returning and shipping costs!!!!

I am sorry for the problem, I will refund you the return shipping cost. Please open a ticket at www.csbooth.com if you have not done so.

pcfr33k wrote: Did you get a chance to look at my initial returned item where the FTDI chip was getting hot and stopped working.
Thanks

I think I have not received your return yet. When did you send it back?

pcfr33k wrote: EDITED:
Will FT_Prog will actually burn into the firmware and do you think I will still need to do this on my last order?
DIYGADGET.COM: Shipment # 231210057516 for Order # 201210032193

Yes, once you program it, it will stay there until you change it again.
for second question, unfortunately yes, because that order was shipped before we found the problem. I am sorry.

pcfr33k

So what s the difference between me programming the chip and if I where to re-order a new one now?
Unless it fails and ruins the bootloader? Other than that if it re-programs with the program link you provided will the EEPROM have exactly the same firmware as in the new ones that will ship out?
This will be the 4th time I am shipping back the TUMPA!!!
I went back and forth with Volkan-k and he thought there was something wrong with my PC/Laptop/Drivers.
I had no problems with other multiple USB to Serial TTL adapters I have and plenty of them.
I tried multiple PC's and even did a fresh re-install of WIndows 7 32 bit.
The back and forth posts was on another thread as well regarding my original TUMPA order from last year. Maybe that could be part of the reason the original unit failed? The FTDI chip was getting real hot and there was no Tx/Rx loopback any longer.
Could it have been this USB to Serial Driver issue? It could have fried out the FTDI chip?

[deleted]

Could you Please use the ticketing system for shipping/returning/billing/sales questions.
You don't have to ship back if the hardware isn't damaged. Please try Mike's how-to guide (instructions to add virtual COM port) first, it will not change firmware (Flash ROM), it will just change configuration in the EEPROM.