Propeller Loader fails to autodetect port

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?

1. Bluetooth serial ports enumerated, no bluetooth serial device attached 
2. In Windows, execute the loader without specifying a "download-to" COM port.

What is the expected output? What do you see instead?

The loader hangs, displaying no output.  Ctrl+c to terminate the program and 
return back to the shell terminal.  

What version of the product are you using? On what operating system?

Latest version of PropGCC.  Unknown loader version (whichever comes with the 
latest downloadable package).  Running on Windows 7 Pro x64.

executing the command "propeller-load -P" to list available ports returns this:

COM1
COM23
COM25
COM40
COM22
COM24
COM39
Standard Modem over Bluetooth link
COM142

COM142 has the Propeller on it.

Original issue reported on code.google.com by Teknicia...@gmail.com on 22 Feb 2012 at 11:27

GoogleCodeExporter commented 9 years ago

Ted, can you retest this with recent loader changes to see if the program still 
hangs? The propeller find function has been enhanced for better performance, 
although not necessarily with this bug in mind.

Original comment by jsden...@gmail.com on 1 Mar 2012 at 7:23

GoogleCodeExporter commented 9 years ago

Oops, I see it's Daniel's report.

Original comment by jsden...@gmail.com on 1 Mar 2012 at 7:24

GoogleCodeExporter commented 9 years ago

Daniel please verify this works or not.

Original comment by jsden...@gmail.com on 24 Mar 2012 at 12:38

sammielove45 / propgcc

Propeller Loader fails to autodetect port #33