Propeller Demo Board Reset

clevin1234

I have loaded a propeller demo board application into EEPROM. With the USB cable connected to my PC the application works fine. If I disconnect the USB cable and restart the application does not work properly. Is there an issue with the reset logic from the USB to RS232 converter on the demo board? If so is there a fix for this? I would like to use the demo board stand alone.

Thanks for your help

grasshopper

The driver (in windows) ask the demo board "Are you there?" When this happens the propeller thinks that its going to be re-programed. My way around this was to insert a jumper between the reset and the FTDI IC.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Visit my site -> [url=Http://www.rawcircuits.com]www.rawcircuits.com[/url]

clevin1234

Do you have any instructions for adding the jumper?

Cluso99

I am not sure I understand your problem.
When you remove the usb cable are you saying the prop resets? (as you unplug)
After you remove the usb cable reset the prop (push the reset buton on the board) does you prop then work correctly?

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Links to other interesting threads:

· Home of the MultiBladeProps:· SixBladeProp, TriBladeProp
· Prop Tools under Development or Completed (Index)
· Emulators (Micros eg Altair, and Terminals eg VT100) - index
· Search the Propeller forums (via Google)

My cruising website is: ·www.bluemagic.biz·· MultiBladeProp is: www.bluemagic.biz/cluso.htm

clevin1234

If I leave the USB cable connected the prop executes the program fine. If I remove the USB cable and cycle power to the prop the application does not work properly. It acts like it keeps getting reset.

luftphoto

This has been discussed in a few threads I think - so you might find more information out there.

If your code tries to load "fullduplexserial" or something similar (even for debugging purposes that aren't used in the final product), that will cause a perpetual reset.

Phil Pilgrim (PhiPi)

This is a known problem with the USB circuitry when it's not plugged into a USB port. Put a 2.2K pullup from A30 to Vdd, and the problem should go away. Here's a link that explains why:

http://forums.parallax.com/showthread.php?p=651731

The pullup isn't really a great solution, since it's actually being used to power the FTDI chip. But until Parallax's USB interface design is changed to include a buffer between the FT232R and the Propeller, it's probably the best we've got.

-Phil

clevin1234

Thanks for all of your help. I removed all of the debug code and everything is working fine now.