#USB TO SERIAL HYPERTERM HOW TO#
#USB TO SERIAL HYPERTERM DRIVERS#

When you say you're trying to 'port' the code from cygwin/avrdude to AVR Studio, you have me puzzled. If you're using FTDI's VCP driver, then any off-the-shelf application capable of talking to a Windows COM port should 'just work' without needing to compile any additional USB-specific code.Ĭould you be more specific about what you're trying to do, and where the problem is coming from? Exactly what are you attempting to compile? You shouldn't need to compile any USB-specific material into any source code that will eventually end up executing within the AVR. The code on the AVR will talk to the FT245 as though it were any other chip with a parallel FIFO interface. I guess I'm just having trouble understanding how libusb is even coming into the picture. You'll need an 8-bit data path, along with appropriately timed strobe pins, to perform the communication. You cannot connect the FT245 family of chips to an AVR's UART, since they actually perform parallel FIFO I/O. (But it should still be relatively straight forward.) That will involve a little more effort on your part.

#USB TO SERIAL HYPERTERM HOW TO#

Maybe you're really stuck on the other end of the equation, namely, how to get the AVR to work with the FTDI chip. The question seems to deal with getting the FTDI chip to work with Hyperterminal, but that's really a no brainer as long as you've properly installed the Windows device driver. It occurs to me that maybe you're putting the cart ahead of the horse, so to speak. Note that this 'virtual COM port' will ignore any baud rate settings you try to provide - since the FT245xx family of chips are actually parallel FIFOs, they will simply accept new data as quickly as the slave device is able to latch data through the buffers. If you use these drivers, your module will show up as a COM port under Hyperterminal (as well as any other Windows software) whenever you plug it in (as long as everything's wired correctly).

#USB TO SERIAL HYPERTERM DRIVERS#

Hyperterminal is already fully capable of interfacing with any device that is registered with the Windows Device Manager as a COM port.įTDI distributes Virtual COM Port drivers for all recent versions of Windows that will work with the FT245xx family of chips. Instead, you should be looking into Windows drivers.

to recompile Hyperterminal with 'built-in' support for FTDI's FT245xx family of USB chips. Since you don't have the source code for Hyperterminal, it won't be possible to use libraries, headers, etc.

Usb to serial hyperterm