Driver fail Windows 10 - Simple IDE with ActivityBoard and ActivityBot
John Kauffman
Posts: 653
in Propeller 1
Using Win 10 and SimpleIDE on one of my laptops: on compile/load, does not see a Prop on COM4. No other COMs are available in the drop-down. I've worked on the problem with this one laptop several different days and with combinations of ActivityBoard, ActivityBoard on an ActivityBot, ActivityBoard WX and 2 Prop demo boards.
I've done following:
Tested combos of boards and cables on other PCs. Problem always remains with this single laptop, not the boards.
Uninstalled SIDE and driver. Rebooted. Installed driver from FTDI site, installed SIDE, rebooted. Same problem.
When connect board to PC, get Windows chimes of new device connected. Only option in drop-down list of ports is COM4. But on load: error of no Prop on COM4.
Possibly useful observation when attach a second board:
When (at same time) plug second prop board into second USB port, I get Windows chimes for new USB device and it appears as a second COM (5,7 or 8). In SIDE, select one of these higher COMs and the SIDE load works fine. But when change to COM4 (first board) the loader fails to see the first Prop. Subsequent boards always work fine, as long as a first board has been attached and is taking COM4.
When start SIDE, always defaults to COM4, even when no prop plugged in.
My best guess:
Could COM4 somehow be used by something else on the PC but is being seen by SIDE as maybe a Prop (Or automatically the default)? Then when SIDE tries to connect, the signal goes to other device and is not recognized by SIDE. Then when add another prop that goes to a non- COM4 designation and works.
Any guesses to fix? I’m wondering if there is a way in the SIDE, driver or Windows to tell SIDE not to consider COM4 a Prop, rather set Prop to another COM.
Thanks.
I've done following:
Tested combos of boards and cables on other PCs. Problem always remains with this single laptop, not the boards.
Uninstalled SIDE and driver. Rebooted. Installed driver from FTDI site, installed SIDE, rebooted. Same problem.
When connect board to PC, get Windows chimes of new device connected. Only option in drop-down list of ports is COM4. But on load: error of no Prop on COM4.
Possibly useful observation when attach a second board:
When (at same time) plug second prop board into second USB port, I get Windows chimes for new USB device and it appears as a second COM (5,7 or 8). In SIDE, select one of these higher COMs and the SIDE load works fine. But when change to COM4 (first board) the loader fails to see the first Prop. Subsequent boards always work fine, as long as a first board has been attached and is taking COM4.
When start SIDE, always defaults to COM4, even when no prop plugged in.
My best guess:
Could COM4 somehow be used by something else on the PC but is being seen by SIDE as maybe a Prop (Or automatically the default)? Then when SIDE tries to connect, the signal goes to other device and is not recognized by SIDE. Then when add another prop that goes to a non- COM4 designation and works.
Any guesses to fix? I’m wondering if there is a way in the SIDE, driver or Windows to tell SIDE not to consider COM4 a Prop, rather set Prop to another COM.
Thanks.
Comments
Then try again
I am using a HP win 10 machine with no problems. even got it set up and working with a PI 3 and dreaded linux!! :clown:
Do other USB devices work on this suspect PC?
Also see if there is a BIOS update from the manufacturer since these will often cure fix hardware issues.
Check that Windows 10 is up to date also.
FTDI devices have unique serial numbers so the system will assign them individual serial ports.