You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Along the way of debugging for Issue #326, I found the code that I believe is causing this, and the way it is written, it treats a potentially-likely response from a connected device (BS2, or otherwise) into a fatal error resulting in toasts instead of a just a prescribed error "Board did not respond..."
Let's discuss the possible resolution once the related code is found again and options are weighed. It is unclear if this is caused by changes in Chrome v61 or not, but the timing of the occurrence is suspicious as we have not seen this error in the years prior.
The text was updated successfully, but these errors were encountered:
Have not seen this error occur since it was reported. Parallax IDE v0.13 or v0.14 may have "fixed" the problem, though we're keeping this issue open for future use as the code involved may need a slight revision.
On 9/18/2017, not long after Issues #326 and #327 occurred, a customer reported this:
Along the way of debugging for Issue #326, I found the code that I believe is causing this, and the way it is written, it treats a potentially-likely response from a connected device (BS2, or otherwise) into a fatal error resulting in toasts instead of a just a prescribed error "Board did not respond..."
Let's discuss the possible resolution once the related code is found again and options are weighed. It is unclear if this is caused by changes in Chrome v61 or not, but the timing of the occurrence is suspicious as we have not seen this error in the years prior.
The text was updated successfully, but these errors were encountered: