IDE not detecting Propellor
A.C. fishing
Posts: 262
I recently got my Propellor Demo Board, and I quickly hooked up my propellor to my pc, but I keep getting:
No propellor found on any COM port
Could not access COM 1
Here's what I did:
Hooked up the prop's power supply to a working outlet.
Hooked the propellor up to the computer via a USB port.
Turned it on... The lights did their little run, and all of them turned on; The 2 lights near the USB plug flashed Red & Blue
Kept it on...
When to the propellor tool and hit F7 to identify device...
And I get this error!
Its probably something simple that I forgot to do...
thanks,
ACfishing
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
No propellor found on any COM port
Could not access COM 1
Here's what I did:
Hooked up the prop's power supply to a working outlet.
Hooked the propellor up to the computer via a USB port.
Turned it on... The lights did their little run, and all of them turned on; The 2 lights near the USB plug flashed Red & Blue
Kept it on...
When to the propellor tool and hit F7 to identify device...
And I get this error!
Its probably something simple that I forgot to do...
thanks,
ACfishing
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
·Somebody said...
-Never Underestimate the power of human stupidity.
Comments
Is its port COM1 USB?
Post Edited (rokicki) : 1/10/2007 12:24:45 AM GMT
What FDTI Drivers??
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
·
http://www.parallax.com/html_pages/downloads/software/ftdi_drivers.asp
I'll try it now.
ACfishing
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
·
No propellor found on any COM port
COM1 Scanned
It seems as if it is only looking at COM1...
But on my computer, COM1 is a serial port!
I thought it was like this for almost all older PCs...
Does it explain this in the manual?
ACfishing
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
·
Goto Control Panel->System->Hardware->Device Manager. Look under Com ports and see if a USB Serial Port shows up.
Mine looks like:
Harrison
I've tried using COM4, but I still get the same message.
What could be wrong?
-ACfishing
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
·
Could it be a problem with the propellor?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
·
And COM4 Scanned?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
·
It seems as if the Drivers are not well installed or some problem in the registration of Windows.
It asks for the people of Parallax:
The use of a COMx can force itself?
>Propeller COM4
A.C. fishing
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
·
If the Propeller Tool doesn't mention COM4, then it never even saw that there was a COM4 to scan.
Try watching the lights near the USB connector on the Propeller Demo Board. Do either or both of them blink when the Propeller Tool tries to identify a Propeller Chip?
If not, try opening your BASIC Stamp editor and then open the Debug Terminal and set it to COM4. If you were able to set it to COM4, try typing on the keyboard, making sure text appears in the Debug Terminal's transmit pane (the white field) and then watch the lights on the Propeller Demo Board's USB connector to see if they blink.
If the PC is able to open COM4 and transmit, you should see one of the lights blink every time you type something in the Debug Terminal's transmit pane.
It is possible there is something wrong with the Propeller Chip or the Propeller Demo Board, however, I don't think so because you are not getting any indication from the Tool that it is even accessing the COM4 port yet.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
--Jeff Martin
· Sr. Software Engineer
· Parallax, Inc.