Skip to content
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

Open
yatch opened this issue May 31, 2019 · 0 comments
Open

Comments

@yatch
Copy link

yatch commented May 31, 2019

If you do something like shown below, some of, or all of the programming tasks could fail:

for mote_id in motes_under_certain_otbox:
   exec "opentestbed/deviceType/mote/deviceId/{mote_id}/cmd/program"
   sleep(3)  // wait for 3 seconds

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.

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.
@yatch yatch mentioned this issue Jun 3, 2019
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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant