On Thu, Jun 7, 2012 at 11:45 PM, Devon Lind <[email protected]> wrote: > One more question though... > I figured out why it keeps changing comports, and that is because > after the module gets programmed I am calling the usb_reset() > function. So that resets the module and that is what takes the device > manager so much time to recognize it and change comports. The reason > I am resetting it though is because I need a way to recognize that the > module has been programmed, and I don't know how to do that other than > resetting the device and checking for the name of the new device in > the device manager. > > So my question; Is there a better way to search for module to check if > they have been programmed using libftdi, rather than resetting the > device and looking for the module that way?
Please tell us a bit more about your device. So your device use the FTDI hardware and you use the libusb-win32 filter driver on top of the FTDI driver so that you can use libftdi (programming) and yet keep the serial port (FTDI driver function), right? So I assume your device has a MCU inside and the MCU has a bootloader inside. Could you just let the MCU reset itself after the programming so that you do not need to use usb_reset to reset the USB interface? How does your bootloader work? -- Xiaofan -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to [email protected]
