has any one got any experience with the ft232r USB to UART chip?http://www.ftdichip.com/Products/FT232R.htm
from the datasheet it looks fairly straight forward.
reading about it on the internet i haven't found anyone else with the similar problems to me. indeed, it seems from all reports a fairly straight forward component.
so, here's the background,
i have made and etched the attached circuit:
i am reasonably sure there are no bad connections or shorts.
when i plug it in on a linux computer it does not appear under /proc/bus/usb/devices.
when it is first plugged in (or when the uhci_hcd driver is removed and reloaded) i get the following output to the sys log at the same time as the RX and TX LEDs flash:
[17180187.476000] usb 3-2: new full speed USB device using uhci_hcd and address 2
[17180187.596000] usb 3-2: device descriptor read/64, error -71
[17180187.820000] usb 3-2: device descriptor read/64, error -71
[17180188.036000] usb 3-2: new full speed USB device using uhci_hcd and address 3
[17180188.156000] usb 3-2: device descriptor read/64, error -71
[17180188.380000] usb 3-2: device descriptor read/64, error -71
[17180188.596000] usb 3-2: new full speed USB device using uhci_hcd and address 4
[17180189.004000] usb 3-2: device not accepting address 4, error -71
so, my hypothysis is that the ft232r must be functional to some extent as the LEDs flash when the relevant driver is reloaded.
i suspect that there some sort of interference going on that is preventing communication between the ft232r and the host computer.
i will try a different USB cable if i can pick one up at work and if that doesn't work, etch another board and rebuild but i'm reasonably confident the circuit is good.
has anyone used this chip before and was it as temperamental as i'm finding it?
could someone compair my schematic to the datasheet and see if i'm missing anything obvious please? (it wouldn't be the first time a dumb typo on my part has had me scratching my head for days...)