Baffling download error

[PropGit]

@dbetz and @AndyLindsay - I don't know what to make of this. Things have been working great for me which integrating PropLoader into BlocklyProp, but suddenly today I can't download to my Propellers reliably.

I'm using two PAB WX boards, each with a Propeller Wi-Fi Module. One is powered by USB, the other by barel jack.

Going right to the PropLoader executable on the command line (in Ubuntu), I get this:


Note that the first attempt's results are what I get most often. The second attempt is slightly different, and rare, and the third attempt results, while it used to be most common, hardly happens anymore (for the moment).

Neither board has anything connected to I/O pins; they're basically factory boards.

[PropGit]

By the way, each are using a different version of Parallax-ESP firmware, one of which is the official v1.0 we released 11/2016. This doesn't appear to be due to anything that changed in firmware. It acts suspiciously like a network flaw, but I have no way to verify that currently. I'll re-test and report more if I have more details later.

[dbetz]

That's odd. The first seems like it downloaded Jeff's second-stage loader but failed to get the initial message from the loader saying it was ready. The second looks like it just couldn't connect to the WX module at all.

[AndyLindsay]

Is SEL connected to 3.3 V? On Mar 24, 2017 1:44 PM, "dbetz" <notifications@github.com> wrote: That's odd. The first seems like it downloaded Jeff's second-stage loader but failed to get the initial message from the loader saying it was ready. The second looks like it just couldn't connect to the WX module at all. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#30 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALCgd7ZaDS8fdT8pA0JNgiBUOfLYHW5Kks5rpCr5gaJpZM4MouRU> .

[dbetz]

SEL is supposed to be connected to 3.3v.

[PropGit]

Had my hopes up... I wish it were that simple.

I've never connected SEL to anything on a regular basis (left it floating), but since you both mentioned that, I've now connected each board's SEL line to 3.3v and verified that the XBee LED is lit green constantly. I can't say for sure that it was lit constantly before, but I think it was, and in my re-tests just before strapping SEL to 3.3v, it stayed green even during moments where it failed to download.

Results after connecting SEL to 3.3v: The problem still occurs, though currently not as often. The difference in frequency of failure has nothing to do with SEL... I tested that.

I'm afraid I'm going to have to install Wireshark on this machine and do some captures and analysis.