No chip found on any port

Dave Goodrich · 2008-06-04 19:50

I am using 9600 baud, no flow control and the latest driver. I get the same error message when I use F7 or try to download a program "No propeller chip found on any serial port".

The same result happens using a demo board on comm5 with built in usb port or the Proto Board on comm7 using the Propeller Plug.

I've tried reseting and various combinations of powering up and attaching the USB cable. I have also tried reducing the latency to 1.

Anything I can try?

Rayman · 2008-06-04 19:56

Do you get any lights flashing on the Prop Plug when you scan the ports? Is the green power light on on the Proto board? Is the Prop logo facing up when you put the Prop Plug on the Proto board?

Dave Goodrich · 2008-06-04 20:56

No flashing lights when scanning for chip on demo board or Proto Board. Lights flash when USB cable is first attached. Prop logo is up and green light on in both cases.

Jeff Martin · 2008-06-04 23:27

Does the error message say that it "Scanned COM5" and "Scanned COM7" and possibly other ports? Or does it indicate some other issue with those ports?

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
--Jeff Martin

· Sr. Software Engineer
· Parallax, Inc.

Dave Goodrich · 2008-06-05 02:14

Says it scanned ports 1 and 2 and either port 5 for the Demo Board or port 7 for the Proto Board.

Cluso99 · 2008-06-05 03:52

Doesn't the port speed need to be set to 115,200 baud ??

Rayman · 2008-06-05 12:56

Maybe this is bad drivers for the FTDI USB serial port...

Try this troubleshooting guide:
http://www.parallax.com/dl/docs/prod/ftdi/USBDriverTroubleshooting-V1.0.pdf

Try not using an external·USB hub (if you are using one).

I think you can test the port by connecting a wire between RX and TX pins of the Prop Plug...· This makes a loop-back connection.
Open the port up with Hyperterminal and see if what you type is repeated on the screen...

Jeff Martin · 2008-06-05 15:26

Cluso99 said...
Doesn't the port speed need to be set to 115,200 baud ??

It actually doesn't matter what the port is configured to by the user because the Propeller Tool will configure it to the proper settings (ie: 115,200, 8 N, 1) each time it opens the port.

At the very least, the blue light should flicker the moment the Propeller Tool accesses the virtual COM port that is logically attached to the hardware.· If there's no blue flickering light, there's some problem (could be driver, as suggested before).· You might try connecting that device, go to Device Manager and find the COM port that belongs to it, right click on it and tell it to uninstall, then remove the device, then go to Add/Remove programs and find every "FTDI" driver item (sometimes there's multiple) and remove them, reboot, the run the latest FTDI VCP driver installation (2.02.4 I think) and then (and only then) plug in the device again and let it enumerate up to the point where the balloon message says something like "Your device is ready to use."

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
--Jeff Martin

· Sr. Software Engineer
· Parallax, Inc.

Dave Goodrich · 2008-06-05 18:22

I manually went in and changed the baud rate to 115,200 and both boards work!

I think my updating to the latest driver may have restored default settings.

Thanks for your help.

Dave Goodrich · 2008-06-06 06:03

The download was still unreliable. Traced the problem to having two hubs in series. Now the problem seems to be solved.

Jeff Martin · 2008-06-06 18:22

Dave Goodrich said...
The download was still unreliable. Traced the problem to having two hubs in series. Now the problem seems to be solved.

Thanks Dave, for letting us know the conclusion; that's good information to have.·

Take care,

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
--Jeff Martin

· Sr. Software Engineer
· Parallax, Inc.

Rayman · 2008-06-06 19:14

Just FYI: I have one computer that occasionally fails to recognize the Prop. (It used to fail to download too, but Prop tool 1.1 fixed that)

I've found that rebooting the computer or sometimes just unplugging and replugging the USB cable fixes the problem for a while...

Frog Man · 2010-04-07 04:49

My computer is only checking Com 1.

I don't know if that's weird, but it's not working.

I didn't use a Prop Plug, I hand made this circuit that you find in books, becausue it's cheaper.

And it is not Identifying my hardware.

Could it be my computer, the program settings, or the circuit board. I have no Idea.

I'm new to all this and really need some help.

Rayman · 2010-04-07 10:16

Is your homemade circuit attached to COM1? It sounds like that's the only port that you have enabled.

I had a lot of trouble with my own homemade circuit, so I'm not surprised you are too...

There are a couple different versions of circuits that Parallax used to recommend. I think there's one in either
the datasheet or the manual. Which circuit are you using?

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
My Prop Info&Apps: ·http://www.rayslogic.com/propeller/propeller.htm

My Prop Products:· http://www.rayslogic.com/Propeller/Products/Products.htm

tonyp12 · 2010-04-07 14:28

Try a dirrent AC Adapter, I have been having problems.
F7 worked 75% of the time.
F10 worked.
F11 always showed: prop lost on com3

Today I tried a different ac adapter, and now it works flawlessly.

Frog Man · 2010-04-07 20:19

I just received a Prop Plug in the mail today and it work perfectly. I am very satisfied.

I am still set on building my own and making it work though.

I'm just curious Rayman, which circuit did you use?

http://i196.photobucket.com/albums/aa51/fd18/prop2.jpg

http://i196.photobucket.com/albums/aa51/fd18/Prop1.jpg

I used the bottom one. I don't know what I did wrong, but my computer simply doesn't recognize any part of it.

Whichever one you got to work, I'm going to keep working on.

Thanks

Rayman · 2010-04-07 21:39

I don't remember if I ever got any of them to work...
I've gone USB and haven't looked back [noparse]:)[/noparse]

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
My Prop Info&Apps: ·http://www.rayslogic.com/propeller/propeller.htm

My Prop Products:· http://www.rayslogic.com/Propeller/Products/Products.htm

DonEduardo · 2010-04-07 22:04

I built the one in the Propeller Datasheet page 5. It served me well. And still does from time to time. Now I mostly use that Nokia cable hack that's on the forums ($3). it allows me to use the USB.

Frog Man · 2010-04-08 06:48

I'm going to attempt the other circuits for something to do.

But I'm just wondering, how did you learn the code?

I see that it's do-able, but so many people are programmers there has to be an easier way that I am not seeing.

Thanks

DonEduardo · 2010-04-08 17:29

The best advice I've seen which also works for me is to just take someone else's code and get it to work. Then, decide on how you would like to make it behave differently (only slightly), and try to understand just enough to perform that one simple change. I've been programing for many many years and am new to the hardware side of things. So learning Spin code for me took almost no time at all. Within a day, along with all the great Objects in the Exchange, I was able to do pretty much what I wanted. The BASIC language always seemed to be a good starting place for people learning to program. Which was my first programming language (on a Commodore 64). I think Spin is probably just as good. On the Sticky of this forum are some education labs that are very good.

No chip found on any port

Comments