-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firmware programming fails when multiple requests come at different timings #102
Comments
yatch
added a commit
to yatch/opentestbed
that referenced
this issue
May 31, 2019
…r each mote This change is applied to only OpenTestbed
yatch
added a commit
to yatch/opentestbed
that referenced
this issue
May 31, 2019
…r each mote This change is applied to only OpenTestbed
yatch
added a commit
to yatch/opentestbed
that referenced
this issue
May 31, 2019
…r each mote This change is applied to only OpenTestbed
yatch
added a commit
to yatch/opentestbed
that referenced
this issue
Jun 3, 2019
…r each mote This change is applied to only OpenTestbed
yatch
added a commit
to yatch/opentestbed
that referenced
this issue
Jun 3, 2019
With this reset, firmware programming succeeds even without time.sleep(2), which is removed by this commit.
Open
yatch
added a commit
to yatch/opentestbed
that referenced
this issue
Jun 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you do something like shown below, some of, or all of the programming tasks could fail:
It seems the cause of the failure is that, an
OpenTestbed
instance uses one single temporary file,firmware_temp
, to keep firmwares to program. Because of this, a firmware image stored in the temporary file could be corrupted by a following request.The text was updated successfully, but these errors were encountered: