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

Can't ever read the firmware version and module ID #31

Closed
snollygolly opened this issue Apr 11, 2016 · 6 comments
Closed

Can't ever read the firmware version and module ID #31

snollygolly opened this issue Apr 11, 2016 · 6 comments
Assignees

Comments

@snollygolly
Copy link
Contributor

On every run of my project, I get the following:

Computer:tessel-ir-utility snollygolly$ npm run tessel

> [email protected] tessel /Users/snollygolly/tessel-ir-utility
> t2 run index.js

INFO Looking for your Tessel...
INFO Connected to Charmander.
INFO Building project.
INFO Writing project to RAM on Charmander (1744.384 kB)...
INFO Deployed.
INFO Running index.js...
Tessel IR Utility is now listening on http://192.168.1.79:8000
Could not retrieve firmware version and module ID. Attempting update.
Uploading new firmware...
Update finished!
Connected to IR!

It looks like it's always updating the firmware, and based on a quick slack conversation with @johnnyman727, that's not expected behavior.

@johnnyman727 johnnyman727 self-assigned this Apr 12, 2016
@johnnyman727
Copy link
Contributor

Yes, it should check if you have the correct firmware version each time but it definitely should not need to update it each time. Thanks for reporting.

@johnnyman727
Copy link
Contributor

johnnyman727 commented Apr 19, 2016

@snollygolly want to try out tessel/attiny-common#9 for me?

If it's easier for you, you can just manually update line of node_modules/attiny-common/lib/index.js to 200.

@snollygolly
Copy link
Contributor Author

@johnnyman727 200 didn't work for me. I upped it in increments of 50, and 700 looks to be about the lowest I can go.

@johnnyman727
Copy link
Contributor

@snollygolly maybe the best way to approach this would be to continually try to communicate with the module after the reset in 50ms increments until we get a response or 1000ms passes. If 1000ms pass, then we can try to update. Do you want to implement that?

@snollygolly
Copy link
Contributor Author

That sounds like a pretty solid idea. I'll sure give it a try!

@johnnyman727
Copy link
Contributor

👍 Fantastic. Ping me when you're ready for a review.

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

2 participants