| Franchised Lines |
| OEM Products |
| Press Centre |
| Case Studies |
 |
 |
 |
|
|
home | about | contact | |
|
 |
Back | ||
|
 |
Sales@alphamicro.net | ||
 |
|
|
|
|
||
|
Frequently asked Questions Are the FT8U232AM and FT8U245AM RoHS compliant? No, and probably never will be. You need to use the newer FT232BL or FT245BL devices respectively and there are differences on 2 pins that you need to be aware of to make the transition (see below). Speak to the Alpha Micro Sales Team for your area for price & availability Are the FT232BM and FT245BM RoHS compliant? No, but simply switch to the FT232BL or FT245BL devices respectively. No changes neccessary to software or hardware. Speak to the Alpha Micro Sales Team for your area for price & availability Is the FT2232C RoHS compliant? No, but simply switch to the FT2232L. No changes neccessary to software or hardware. Speak to the Alpha Micro Sales Team for your area for price & availability Looking to convert an existing FT8U232AM design to use the FT232BM? There are only 2 items you need to check to convert an existing design to use the BM chip: a) TEST (Pin 5) becomes an RSTOUT (output) so if currently connected to GND, cut the track or leave unconnected. b) RCCLK (Pin 31) becomes the TEST pin so remove the pull-up resistor and capacitor & short pin31 to GND. Do I need to fit the EEPROM? The chip has in-built default parameters in silicon but if you need to change any of the following you will definately need to fit the EEPROM to be able to store your preferences: USB Power draw, Product ID, Serial number or the plug-and-play flag. Additionaly the following requirements would necessitate updating (and therefore fitting) the EEPROM: - If more than one of your device needs to be plugged into the same PC at any one time. - If you require only one driver installation per PC, fix the serial number to be the same on all devices. - If you need to set the PID as provided by AMC or the USB Forum to work with your drivers. How do I program the EEPROM? Grab MPROG and the user manual, this will allow you to program the FTDI device via the USB, you will need to load the DLL driver for this to work (and therefore remove any VCP drivers on the PC) but you can program more than one device at once. What happens if Windows does not detect my device when I plug it in? Two possibilities: 1) The device is not powered up, particualty common mistake with the DIP modules as the USB power, core Vcc and I/O power need to be fed - quick fix is to link these pins together. 2) The device has a different PID to that in the driver. Common when you have your own PID and device may not be programmed to this. Grab USBVIEW and see what the Host Controller thinks it is. Driver loads but no data goes to or fro? Have you loaded the VCP driver AND the DLL drivers on this PC? Win98SE tends to give the 'Blue Screen of Death' if this happens. Visit the Control Panel and use Add Remove Programs to eliminate the offending driver. Windows installs the VCP Drivers but no Com Port is available? Sounds like the Virtual Com Port (VCP) driver did not in fact install, the Silicon Driver needs to install successfully and then the VCP driver can be installed so in fact there are 2 stages to the Driver install, users can abort the second thinking that it is a mistake. Go to Device Manager, click on the USB device and hit Update Driver. Can't quite find what you are looking for? Why not contact the Alpha Micro Support Team(contact us) or visit the product pages at www.ftdichip.com Last Updated: 28/10/2006 05:02:17 |
||
|
home | franchised lines | oem products | press centre | site search | privacy policy | ||