Proto board and regular serial interface instead of USB issue
Rayman
Posts: 14,789
I had an extra proto board but no more USB interfaces to go with it, so I built the little circuit in the documentation to connect with a regular RS-232 serial port on my computer...
Strange thing is that it only works when directly connected to the port on the back of my computer!· When I try to bring it out with a regular 6' straight-through extension cable, it doesn't work (the Propeller Tool doesn't find it).
Isn't this strange?· Is the Prop Tool trying to connect at some insane speed that doesn't work over an extension cable?
I looked in all the documentation I have and can't find any mention of what rate the Prop and the Prop tool are communicating...
It's a bit inconvenient to crawl under the desk and hook it up right now, so I'd appreciate any suggestions!
Can I lower the com rate between Prop and Prop Tool?
Strange thing is that it only works when directly connected to the port on the back of my computer!· When I try to bring it out with a regular 6' straight-through extension cable, it doesn't work (the Propeller Tool doesn't find it).
Isn't this strange?· Is the Prop Tool trying to connect at some insane speed that doesn't work over an extension cable?
I looked in all the documentation I have and can't find any mention of what rate the Prop and the Prop tool are communicating...
It's a bit inconvenient to crawl under the desk and hook it up right now, so I'd appreciate any suggestions!
Can I lower the com rate between Prop and Prop Tool?
Comments
Why do you assume that it is a speed issue? The RS-232 drivers are normally only rated up to 115K baud and no way that would ever be a problem over 6' of cable.
The most logical conclusion would be your "regular" cable, is there really such a thing? Make up your own or at least check the cable with a meter which is surely a lot less inconvenient then crawling under a desk.
*Peter*
Things to check:
1. Is the cable good? Have you used it before?
2. Are all of the lines connected in the cable, including DTR? Otherwise it won't reset the chip.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
The more I know, the more I know I don't know.· Is this what they call Wisdom?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Brian
uController.com - home of SpinStudio
Graham
- If you don't want to write a program just use an LED
- Check the reset pulse! Sometimes funny connections are inside a sub-D plug wrt DTR, CTR, and RTS
I think I did find a fix though. I don't understand why, but adding a 0.1 uF cap between reset and ground solves the problem...
This cap will most like extend the reset-down time. So it seems possible that your differenciating series cap in the DTR line was too small..
Generally a 10nF + 10k high-pass at a transitor base is fine, as done on the demo board....
Modestly I suggest you to try the following:
1-So, do a little code communicationg the propeller with the PC at 2400 bps sending some text lines.
2-Use no cable to download the code to the pchip.
3-Use hyperterminal to check the code and data sent with NO cable attached.
4-Connect the cable after get all work and try again..
5-If·still wont work, check the cable again and again, no proper shield could be the problem at high rate speeds. If this work at 2400 bps you're proving that.
I used that circuit exactly as it appears in the datasheet , and it works fine for me. Do you assemble it more or less "appropriately" ?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Regards.
Alberto.
I mean I used the serial circuit to program the propeller...I assembled that with a pchip, xtal, eeprom, in a board.
Point 2.3.2 in page 5. Schematic point 2.3.1 of pchip datasheet. I used a homemade 3 ft serial cable.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Regards.
Alberto.
no probs,works absolutly fine with Hippy's VBLOADER, but not got it to work
yet with DOS under FPC ( but that's my problem )
Hippy I need your expertise,I've probably got a timing problem!!
:- Wouldn't it be nice if the Wattage of a car stereo couldn't exceed the
IQ of the driver.
Regards to All
Ian
Glad to hear my loader's working. As to expertise, you may be over-rating me, but you're welcome to run anything past me and I'll give it my best shot.
A problem I found was that too long between any pulses and the Propeller timesout or something, communications is lost. I found the best thing was small buffers rather than large and keep the data churning out as quickly / as frequently as possible. In real world terms, keep the PropPlug blue Tx Led on as much as possible rather than pulse-gap-pulse.