FTDI win 7 64 bit issues
DigitalBob
Posts: 1,513
in Propeller 1
Win7 would not recognize the Usb . The techs at Parallax where helpful but no cigar. So I called FTDI the tech suggested that I download the exactable on the right side of the older driver 2.10 save it then right click and run as administrator .He also suggested that I run the CDM uninstalled . I'll try it and let you know. He also said that a lot of people are having trouble with the win 7 64 bit .
Comments
Although my usb arduinos work fine a ftdi based usb to serial adapter for a pro mini had the same issues.
I'll keep a look out here to see if the issue gets resolved.
P.S. I was about to post the same as you but thought why has this not been brought up before so I didn't.
Are these Parallax products that you are having trouble with?
I have Windows 7 64-Bit and I have never had a problem using the Parallax Serial Adapter, Propeller QuickStart, Propeller Activity Board, or Propeller Demo Board which all use FTDI chips.
I have seen USB connectors and cables go bad so try another USB cable, try all the USB ports, and try another computer.
Do you have the latest BIOS, drivers, and software updates?
Problems have always been bad cable. You need to try at least three cables. I have thrown out at least a half a dozen.
Anyway thanks for everyone's input. There are some very intelligent members on this forum some of you guys should be working at MIT, NASA etc.
Does your homemade Prop Plug work on other Win 7 computers?
As a sanity check I would look at all the solder connections and make sure all the parts match the schematic.
If it still doesn't work then ask Parallax Tech Support to verify that Prop Plugs are built using the published schematic.
I also find it odd that dropping a board would cause the FTDI chip to come loose.
I would have expected a connector to break first.
In the future I would call Parallax first before attempting to repair it since this could have been a defect.
I think you must have something wrong with your board.
But, it is hard to imagine why it would work on old windows and not new windows... Very strange...
Thanks again
What was the actual PCB change that fixed it ?
Sounds more like a Chipset/Hardware issue & you just fluked a 'good' (extremely tolerant) chipset on the Laptop.