USB "set options" error

[phil-pilgrim]

I get the below-illustrated error quite often. It happens with a Propeller Activity Board whenever I power it off and back on -- once in a while at other times, too. The USB is still connected and recognized by Solo and my PC (Win 7). I have to unplug the USB connector, wait for the port to disappear from the Solo menu, plug it back in again, and wait some more for it to reappear. I do not have a similar issue with the Propeller Tool, for example.

[PropGit]

Thank you, @phil-pilgrim. I've been trying to find the source of this problem and your details help me track it down. Prior to your report, I was not able to determine anything that makes it happen deterministically. I'll try your tests and report back here.

[PropGit]

Actually, this is a problem that seems fully involving BlocklyProp Launcher and not Solo directly, so I'm transferring the issue from Solo to the Launcher repository.

[PropGit]

Version 1.0.1 will be release 5/22/2020. It may have fixed this issue. Please verify.

[phil-pilgrim]

Latest release on Parallax website is still 0.11.2.

[zfi]

The 1.0.1 installers for Windows and MacOS have been deployed to Solo and the Parallax web site.

[PropGit]

The Parallax website has been updated this morning as well.

[phil-pilgrim]

I'm sorry to report, but I still get the same error. Moreover, even when it "works," I sometimes have to wait seven or eight seconds after I see Download... for the actual downloading to begin. Also, if I try to download with the USB cable plugged into the Activity Board, but with the power turned off, I get the Cannot set port options error, instead of "No Propeller found." Finally, downloading never works after the first time the USB cable is connected. This is what I see:

The second attempt works, though, unless I get the Cannot set port options error.

Just to verify:

Again, running Chrome on Win7.

[zfi]

@phil-pilgrim: Are you running this on solo.parallax.com or blockly.parallax.com? We have tested both sites extensively and have not seen the issue you are noting after the 1.0.1 Launcher release.

[phil-pilgrim]

https://phil-pilgrim.github.io/solo/blocklyc.html

[zfi]

Can you try this on solo.parallax.com and see if you have better results?

[PropGit]

I just did 25 successful downloads from your site.

This may be a hardware/timing difference I can't duplicate.

Please click on the Launcher's gear icon and check Verbose Logging, then do a download and past a screenshot. Here's mine from a download via your Solo site:

[phil-pilgrim]

On solo.parallax.com now:

1. With the USB cable plugged in, and with the Activity Board power off, I don't get any error; it just hangs after Download...

2. After unplugging the USB cable, turning on the AB, then plugging in the USB cable, and waiting for the port number to appear in the drop-down menu, a download hangs for awhile before I get the Cannot find port error.

3. Second time I got a successful download, but only after waiting a minute or more for it to begin.

4. Third and subsequent times, same thing. During the wait, there is no activity indicated by the AB's USB LEDs. Also, COM101 remains displayed in the drop-down menu.

Okay, log stuff to follow...

[PropGit]

The verbose logging starting before you plug in the USB port may help us too. I've seen some systems make the port available, but then preempt more CPU time for any software that tries to open it for a while (presumably because the kernel is still configuring something). Along that note, if you attempt a download with Propeller Tool right after plugging the USB cable back in, does it download immediately?

[phil-pilgrim]

With AB off and USB plugged in:

After turning on AB with USB still plugged in:

Second attempt with AB still on:

Unplug USB, then plug it back in:

I got no successful downloads during this test sequence.