To make the name effectively changed, you do not need to reboot the computer, replug-in the nano, and it works fine, or juste call the CYCL 0 command whithin the terminal of FT_prog, and it works fine too for the nano device. This page only contains detailed info on how to uninstall FT_Prog in case you decide this is what you want to do. Click and hold (or right-click) the Start button, then choose Device Manager. Given your line about the driver needing to be installed for FT_PROG to work, this definitely seems to be the overall problem. Notice that when you click FT_Prog in the list of apps, the following data about the program is shown to you: Safety rating (in the lower left corner). devicelist[i].Description, but also; devicelist[i].SerialNumber, both can be re programmed with FTDI utility FT_Prog.exe or with some custom code, this is what I do for the device … Look for your connected device (such as Apple iPhone), then right-click on the device … This page is not a recommendation to uninstall FT_Prog by Future Technology Devices International Ltd. from your computer, we are not saying that FT_Prog by Future Technology Devices International Ltd. is not a good application. If the operating system does not have a driver for your hardware installed the device will not function. You should see four ports. httpstackoverflow.comquestions9264312detecting-correct-device-using-ftdi-ftd2xx-net. You can find the Device Manager control panel by right-clicking My Computer and selecting properties. Ft_prog works for nano device! See FTDI FT_PROG programming tool to find out how to download and install this tool. If it is installed on your PC the FT_Prog application will be found automatically. All the hardware driver issues disappeared. In order to check the version you need a software like usbview or usbdeview (both freeware and don't need any installation). Run FT_PROG and find your attached device, as described in FT_PROG GUI application. This is the cause of the problem. Select the Hardware tab and click Device Manager. Then reconnect your device. I have dug a little further, the 64-bit Windows OSes do not work well with some hardware drivers. 4.1.I had used FT_Prog previously to solve issues related to Uniflash not recognizing the devices, but now the drivers are not working. If the device doesn't respond or responds with the wrong value then I know it's not the one I'm looking for. The FT_prog can modify the name of nano. In the Device Tree view, expand the Hardware Specific section. Run the software and look for the "USB serial converter" device which is the one I tried different methods to force the installation of the drivers, but none seems to work. You cannot revert back the changes because the device is not longer discovered by the drivers. Navigate the list of programs until you find FT_Prog or simply activate the Search feature and type in "FT_Prog". I have downloaded it but I have not had time to see if it fixes the driver problems yet. Locate and expand the Portable Devices section. Which means that any subsequent attempt to use FT_Prog with the serial to USB converter will not work! If iTunes opens, close it. Now there is an OpenOCD 0.5.0 dev version being developed for 64-bit OS. Device Manager is used to control attached hardware to your computer. You know the COM port number currently assigned. Not every ftdi chip has faulty drivers, so the first step is to check the chip's driver version. As mentioned above you could use. The drivers should be installed or the FT_PROG won’t pick up the device (you can install the drivers by the outlined procedure or manually), and of course the device you want to reprogram shoud be connected to USB. After opening the program press the magnifying glass icon to scan for devices (or F5). Thank you for your answer and for the solution. When you change the default FTDI VID and PID descriptors, matching against the original, FTDI drivers will not work anymore! Search for this (ie: COM23) using the Edit->Find function in regedit.exe. Hello, I have two CC3200, one Rev 3.2 and the other Rev. In device manager, it still shows no driver and I'm not sure where to manually point it to find the driver. 4) If you do not have control over the target device where you can imbed a unique ID value, all is not lost.