Usb Vcom Port Driver Mtk

[Demeter Exekutor]

VirtualCOM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC. Application software can access the USB device in the This page contains the VCP drivers currently available for FTDI devices.

Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC. Application software can access the USB device in the same way as it would access a standard COM port.

If a custom vendor ID and/or product ID or description string are used, it is the responsibility of the product manufacturer to maintain any changes and subsequent WHCK re-certification as a result of making these changes.

CountryAfghanistanAlbaniaAlgeriaAmerican SamoaAndorraAngolaAnguillaAntarcticaAntigua and BarbudaArgentinaArmeniaArubaAustraliaAustriaAzerbaijanBahamasBahrainBangladeshBarbadosBelarusBelgiumBelizeBeninBermudaBhutanBoliviaBosnia and HerzegovinaBotswanaBouvet IslandBrazilBritish Indian Ocean TerritoryBrunei DarussalamBulgariaBurkina FasoBurundiCambodiaCameroonCanadaCape VerdeCayman IslandsCentral African RepublicChadChileChinaChristmas IslandCocos (Keeling) IslandsColombiaComorosCongoCook IslandsCosta RicaCote D'IvoireCroatiaCubaCyprusCzech RepublicDenmarkDjiboutiDominicaDominican RepublicEast TimorEcuadorEgyptEl SalvadorEquatorial GuineaEritreaEstoniaEthiopiaFalkland Islands (Malvinas)Faroe IslandsFijiFinlandFrance, MetropolitanFrench GuianaFrench PolynesiaFrench Southern TerritoriesGabonGambiaGeorgiaGermanyGhanaGibraltarGreeceGreenlandGrenadaGuadeloupeGuamGuatemalaGuineaGuinea-BissauGuyanaHaitiHeard and Mc Donald IslandsHondurasHong KongHungaryIcelandIndiaIndonesiaIran (Islamic Republic of)IraqIrelandIsraelItalyJamaicaJapanJordanKazakhstanKenyaKiribatiNorth KoreaSouth KoreaKuwaitKyrgyzstanLao People's Democratic RepublicLatviaLebanonLesothoLiberiaLibyan Arab JamahiriyaLiechtensteinLithuaniaLuxembourgMacauFYROMMadagascarMalawiMalaysiaMaldivesMaliMaltaMarshall IslandsMartiniqueMauritaniaMauritiusMayotteMexicoMicronesia, Federated States ofMoldova, Republic ofMonacoMongoliaMontserratMoroccoMozambiqueMyanmarNamibiaNauruNepalNetherlandsNetherlands AntillesNew CaledoniaNew ZealandNicaraguaNigerNigeriaNiueNorfolk IslandNorthern Mariana IslandsNorwayOmanPakistanPalauPanamaPapua New GuineaParaguayPeruPhilippinesPitcairnPolandPortugalPuerto RicoQatarReunionRomaniaRussian FederationRwandaSaint Kitts and NevisSaint LuciaSaint Vincent and the GrenadinesSamoaSan MarinoSao Tome and PrincipeSaudi ArabiaSenegalSeychellesSierra LeoneSingaporeSlovak RepublicSloveniaSolomon IslandsSomaliaSouth AfricaSouth Georgia & South Sandwich IslandsSpainSri LankaSt. HelenaSt. Pierre and MiquelonSudanSurinameSvalbard and Jan Mayen IslandsSwazilandSwedenSwitzerlandSyrian Arab RepublicTaiwanTajikistanTanzania, United Republic ofThailandTogoTokelauTongaTrinidad and TobagoTunisiaTurkeyTurkmenistanTurks and Caicos IslandsTuvaluUgandaUkraineUnited Arab EmiratesUnited KingdomUnited StatesUnited States Minor Outlying IslandsUruguayUzbekistanVanuatuVatican City State (Holy See)VenezuelaViet NamVirgin Islands (British)Virgin Islands (U.S.)Wallis and Futuna IslandsWestern SaharaYemenDemocratic Republic of CongoZambiaZimbabweMontenegroSerbiaAaland IslandsBonaire, Sint Eustatius and SabaCuracaoPalestinian Territory, OccupiedSouth SudanSt. BarthelemySt. Martin (French part)Canary IslandsAscension Island (British)Kosovo, Republic ofIsle of ManTristan da CunhaGuernseyJersey

***Windows 10 and Windows 11 only. Universal Windows Drivers enable developers to create a single driver package that runs across multiple different device types, from embedded systems to tablets and desktop PCs.

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

I have a LM4F120 launchpad. I am making extensive use of the virtual com port and I find it's receiver (data sending from LM4F to PC) will just stop for some reason. If I connect up an rs232 interface and use a real com port, the exact same code runs fine. It doesn't much matter as my target design will use a real com port, but I wondered if anyone else had this problem. Also how do I check if I haver the latest FTDI driver and where would I get it from?

Well yes, thanks, I've been there of course, but the version numbers don't make sense. Perhaps I should have said where do I find the latest "stellaris virtual serial port" drivers? The one on my pc says v2.0.9270.0 dated 3/8/2012, which sounds old to me. I have great difficulty with the TI site just not responding so searching is almost impossible for some annoying reason.

I may have seen this issue earlier. Is this a Windows7 PC? There is an option in the device manager (in case it is a Windows7 PC), where the USB port gets powered/disabled if let idle. The option is selected by default as a Power Saving Option. Unselecting this may help if my hunch is correct.

Thanks Amit, this is a Windows7 PC. I can't find the setting you refer to but there's no evidence of the power going off ie the launchpad stays running, but it's a good idea, I'll keep looking around the power options. Eventually I found by uninstalling and ticking the delete files box I could change the version of the "Stellaris virtual Serial port" driver, but all the versions I have (from the various Stellarisware and Tivaware that I have) behave the same. I did also find the place to download them from on the TI site too, although these appear to be older still!

So far I have not seem a problem with FTDI drivers on WinXP, but on Win7 this did happen. I agree the Power to the board used to be turned off in my case, which got restored if at any time I moved the mice/keyboard, but Serial Port did not recover. It is worth the effort to eliminate this before checking for the FTDI driver versions.

During development, usually due to programming errors, one has to reset, repower, go to beginning of main in debugger etc. many times. As you say, sometimes the virtual serial port does not stand up to this treatment and stops working. It can be very frustrating hunting for a software problem which turns out to be the serial port driver. I now usually leave my scope monitoring the rx and tx lines to be sure.

If the above didn't help or you already have the drivers installed and you still have no contact to the control system, go into device manager and delete all of the ports in the Ports (COM LPT) section.

Then, disconnect and reconnect the control system and wait for the driver to automatically install.

I downloaded the example (RTOSTutorial_Ex10A-LPC18xx) for theLPC1857 and modified it to match my hardware. ( took out the graphicscontroller, changed the USART from 3 to 0. Pulled USB1 from the runtime environment. Removed SPI. Changed the CPU to LPC1837. Updatedthe pinouts in RTE_Device.h... I am not using PPWR, PWR_FAULT, andINDI1 on this USB port. )

However when I plug into a Windows 7 or Windows 10 PC nothinghappens in device manager. Even if I have the driver wrong I shouldsee something happen when I attach the board. I did go ahead andinstall the VCOM driver that was included with the example.

3a8082e126