Propeller Chip: No Propeller Chip Found on any serial port.
eWizardII
Posts: 20
Hello,
I have read through various post on people's propeller chip's having this same problem. However none seemed to solve the problem. I believe I have installed the correct driver from FTDI (since I installed that first on the machine and then plugged in the prop and then added a 9V bat.). My first attempt I tried multiple times without success then one time upon transferring ir_oscope.spin (the program I had been trying) it worked, however the terminal did not load (but that is a different problem, I may have misread the code and really props do not have a debug terminal - blue screen like Basic stamps ?). Nevertheless I was reading one of the prop guides from parallax, and it said to check the rails, so I checked they were not 3.3V, so once I fixed that issue, I tried again. To no avail. What I have been trying is the following:
(1) usb cable is already plugged into PC
(2) Plug usb cable into prop ' the light is a dim green and there is a flash of both lights on the usb FTDI device that's on the board
(3) Plug in battery ' the light glows a solid green
(4) Attempt to detect prop ' a blue light flashes as the pc is scanning the com ports
(5) PC claims : No prop found on Com 5 in my case ' Although when it gets to that com port that it is actually on the blue light flashes - so it's like it knows it is there but at the same time it doesn't.
Please help me in diagnosing this problem.
(I have tried changing pcs, tried change the baud rate, reinstalled drivers and restarted, changed the latency -- all to no avail)
Post Edited (eWizardII) : 7/5/2008 4:18:23 AM GMT
I have read through various post on people's propeller chip's having this same problem. However none seemed to solve the problem. I believe I have installed the correct driver from FTDI (since I installed that first on the machine and then plugged in the prop and then added a 9V bat.). My first attempt I tried multiple times without success then one time upon transferring ir_oscope.spin (the program I had been trying) it worked, however the terminal did not load (but that is a different problem, I may have misread the code and really props do not have a debug terminal - blue screen like Basic stamps ?). Nevertheless I was reading one of the prop guides from parallax, and it said to check the rails, so I checked they were not 3.3V, so once I fixed that issue, I tried again. To no avail. What I have been trying is the following:
(1) usb cable is already plugged into PC
(2) Plug usb cable into prop ' the light is a dim green and there is a flash of both lights on the usb FTDI device that's on the board
(3) Plug in battery ' the light glows a solid green
(4) Attempt to detect prop ' a blue light flashes as the pc is scanning the com ports
(5) PC claims : No prop found on Com 5 in my case ' Although when it gets to that com port that it is actually on the blue light flashes - so it's like it knows it is there but at the same time it doesn't.
Please help me in diagnosing this problem.
(I have tried changing pcs, tried change the baud rate, reinstalled drivers and restarted, changed the latency -- all to no avail)
Post Edited (eWizardII) : 7/5/2008 4:18:23 AM GMT
Comments
Try:
- preferences
- edit ports
- restore defaults
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Aka: CosmicBob
Make sure you have the latest Prop Tool (v1.2)
So...
I decided to install the FTDI drivers from the http://www.parallax.com/tabid/442/Default.aspx (Propeller Download Page) as opposed to the http://www.parallax.com/Default.aspx?tabid=530 (FTDI USB Driver Page). After I selected the FTDI port driver for both the COM port and the serial port I proceeded to test software again this time before it starts it says:
Last Session (1 minute) ago experience a fatal serial port error on:
COM 10: USB Serial Port
I have attached an image of what my drivers say.
Post Edited (eWizardII) : 7/5/2008 4:14:50 PM GMT
Leon
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Amateur radio callsign: G1HSM
Suzuki SV1000S motorcycle
Propeller, of course.
Leon
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Amateur radio callsign: G1HSM
Suzuki SV1000S motorcycle
If you don't have a scope you could simply check the relevant solder joints. It might be easiest just to return it for a replacement. I'm assuming that the USB port you are using is working properly, of course.
Leon
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Amateur radio callsign: G1HSM
Suzuki SV1000S motorcycle
Ray
The first time I wired up my PE kit, I did not get anything, I was not a happy camper, so I just ripped everything out, and started from scratch( I think I did it a couple of times)·. If I would have known what the minimum build was, I would have saved a lot of hair from the top of my head. Have fun.
Ray
Ray
If the regulator is fine then like suggested before check your wires.
If the computer detects the FTDI USB->Serial adapter then I can't see how it could be computer related.
Make sure that the + out from the regulator goes to VDD of the prop, and GND goes to GND/VSS of the prop.
Other than that it is really hard to say what to do without actually being able to look at your setup.
Maybe you could take a picture of it and post it for us to look at.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Check out my robot using the propeller RECONAUTOR
If you like my avatar then check this out Propeller Domed Stickers for sale
Building Blocks To The Propeller Chip
If you need a closer picture of a particular section, please say so.
1. Make sure that the prop plug is all the way on, when you first use it, it might take a bit of effort to get it to push all the way onto the pins.
2. Make sure that the reset button is on the right way use a multimeter to test that there is no continuity on the two pins (with wires attached) when the button is not pushed.
3. If there is then rotate the button 90deg leaving the wires where they are.
4. Check that there is 3.3v on the actual propeller chips pins (VDD and VSS) using a multimeter.
Hope this helps.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Check out my robot using the propeller RECONAUTOR
If you like my avatar then check this out Propeller Domed Stickers for sale
Building Blocks To The Propeller Chip
To avoid the harsh light created by the flash, you can taping a piece of white paper in front of the flash tube to diffuse the effect.
Leon
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Amateur radio callsign: G1HSM
Suzuki SV1000S motorcycle
I would also double check the voltage at you RESn pin. A pulse low on this pin is used for identification. Make sure you read Vcc there. The pulse low may be too fast to see with a multimeter though...
1. Check
2. Check
4. [noparse][[/noparse]Only the battery was plugged in 9.58V]
GND - RESn 3.44V
3.3V - GND (Left Side) 3.64 V {Oddly it increases if I leave it connected long enough at .01V}
3.3V - GND (Right Side) 3.52 V {Oddly it increases if I leave it connected long enough at .01V}
____
Thanks for the note, I'll try another breadboard before looking at PCBing it.
____
I don't see the power bus problem, could you give me coordinates, thanks.
I checked the RESn pin voltage.
Battery Plugged in 3.41V {Oddly it increases if I leave it connected long enough at .01V}
USB Plugged in 0.00V
Battery + USB 3.48V {Oddly it increases if I leave it connected long enough at .01V}
Running detection...
still remains around 3.48V
I also tried an LED at the 3.3v locations on the prop, certainly brighter than the default green LED on the board, likewise at the RESn and GND section it is a lot dimmer than the other points on the board, it is about as dim as just plugging in the USB cable only. The voltage across my board's LED is about 2.3V.
Other than you've disconnected the eeprom I didn't see anything wrong with you setup, reset button looks fine too.· Though one thing you might want to do is, clean up the wiring to something close to whats inside the lid of the·PE Kit lid, it makes troubleshooting wiring very simple.
Attached is a poor picture of my board for comparison.
I hate to even suggest this but it might be a bad prop chip.· I don't beleive it has anything to do with the prop plug since you said the blue light does blink when checking for the chip (dont believe it's the driver either).· So it's either got to be in the wiring (which I know you've checked, so doubt this) or the chip (which might have been damaged by the earlier troubles you had, though this is unclear).
So really at this point I'd suggest calling their tech support, the number is on the bottom of page 12 in the PE-Lab-Setup pdf file.
Sorry I couldn't solve your problem, good luck.
P.S.
··· Ignore the extra cap on my board where the battery is plugged in, it's there because I use a wall wart for power.
I'm sure that nice picture will help.
I doubt the Prop Plug is the problem, but it might be fun to check this anyway...
Post Edited (eWizardII) : 7/7/2008 4:23:18 AM GMT