rshell.py nowait replaced by wait (seconds). Requires pyboard.py dated 8th Dec … #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an interim fix to the issue of the behaviour in the case where the pyboard is not ready when rshell is started. If pyboard.py fails to connect in time, rshell prints a message and issues exit(1). I appreciate that your preferred approach is to raise a DeviceError. However if I do that it attempts to autoconnect which then throws an exception and hangs. Until that's fixed it seemed cleanest to quit.
Here is the outcome with a non-ready Pyboard using DeviceErrror
I have