Hi,
Was wondering if anyone can share some simple, test code for operating the FTDI FT232BM, or the FT232RL (The break out board from SparkFun).
Thanks,
Tony
Hi,
Was wondering if anyone can share some simple, test code for operating the FTDI FT232BM, or the FT232RL (The break out board from SparkFun).
Thanks,
Tony
Last edited by TonyA; - 23rd April 2007 at 17:14.
The FT232xx is a USB-Serial adapter chip. Plug it into the USB port of the PC and it becomes a virtual com port, so you use Hyperterminal (or whatever) on the PC like you would a normal serial port.
At the PIC's end, the FT232xx turns the USB into a serial port. Some PICs have serial ports. All programs for PICs compiled by PBP have the ability to either use the hardware serial port or to 'bit-bang' a serial port on almost any available pin.
It couldn't be any simplier. But, we don't know what kind of PIC you're using, we don't know what kind of hardware you have built up, we don't know what kind of test code you want to use (loopback, read a button, light an LED), we don't know anything!
Hi,
Thanks.
I haven't chosen a PIC to use for this yet, any recommendations?
I was just looking for some PBP code to get me started. I have a very simple program written in Python that sends serial data. I just want to light up an LED attached to my pic to get started.
PC ---> Serial out via FTDI chip ----> PIC = light up an LED when serial data received.
After that I'll go the other way, receiving data to my PC from the PIC
(Just very, very simple to get started.)
The FT232RL (The break out board from SparkFun) looks really nice and inexpensive.
Thanks again,
Tony
Hi,
Thanks again.
So, it would be exactly as if it were just plain serial input?
I thought maybe there were some other things needed to do in dealing with the bridge chip. (Is there any "handshaking" or clock data that needs to be sent/received between the Pic and the FT232XX?)
(Sorry in advance if I'm causing any confusion, etc. I'm just now starting to learn about rs232 and FTDI)
Thanks again,
Tony
The basic operation is just as simple as that. CTS/RTS are optional, programmable. The biggest pain (if you can call it that, 'cause it's all handled by Windows) is getting the thing recognized by Windows. If you don't mess with the drivers and install them correctly, no problem.
Bookmarks