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

'tilda_tools reset' gives obscure error if copy_via_repl_header.py not on badge #142

Open
jburgess777 opened this issue Sep 9, 2018 · 0 comments

Comments

@jburgess777
Copy link

I bootstrapped my badge over wifi and then tried to use tilda_tools reset to put the badge into a known state but this always gave obscure errors:

[jburgess@localhost Mk4-Apps]$ ./tilda_tools reset
Connected to badge: DONE
Stopping running app: DONE
could not exec command (response: b'>>')
[jburgess@localhost Mk4-Apps]$ ./tilda_tools reset
Connected to badge: DONE
Stopping running app: DONE
could not exec command (response: b'",')
[jburgess@localhost Mk4-Apps]$

going to the repl with minicom I got a clue that h was missing:

Press CTRL-A Z for help on special keys                                                                       
                                                                                                              
                                                                                                              
Traceback (most recent call last):                                                                            
  File "<stdin>", line 1, in <module>                                                                         
NameError: name 'h' is not defined
>>> 

After some more digging I see that h() is defined by copy_via_repl_header.py and that only gets copied to the badge if you use something like tilda_tools sync. It would be nice if the reset code had some better error checking or could automatically copy across this file.

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