Ensures firmware file will be deployed to T2 and updates deps

[johnnyman727]

Should be merged after tessel/attiny-common#4 is deployed to npm.

[rwaldron]

Is there any easy way to confirm that the firmware has been pushed out to the attiny?

[johnnyman727]

@rwaldron I think the best way would just be to use fs.exists. Are you hinting at some missing units tests? :)

[rwaldron]

No no, I meant on the actual μC itself... I have an attiny programmer and I'm wondering if I can use that to just confirm for myself?

[johnnyman727]

Oh gotcha. You can modify the code to just call the function to check the code CRC upon initialization and confirm that it matches the expected CRC.

[johnnyman727]

Okay I finally got around to testing this on T1. It looks like firmware updates have been non-functional on T1 for some indefinite amout of time. I reported the issue here: tessel/attiny-common#6.

I also found out that updating doesn't always work on T2 (potentially due to the same root cause(s)). Those issues have been reported as #50 and tessel/attiny-common#5.

Seeing as these issues have existed prior to this PR on T1 and it only adds functionality for T2, there is no reason not to merge this PR now and put out an npm release that allows the module to be used on T2.

[johnnyman727]

I haven't heard any dissenting opinions so I will move forward with releasing new versions of avr-isp, attiny-common and this ambient module (with this PR).

[rwaldron]

@johnnyman727 I've been trying to get my ambient module updated for hours and it just won't work, any ideas? When I look at the files that get deployed, everything is there, but regardless:

$ t2 run index.js
INFO Looking for your Tessel...
INFO Connected to bishop.
INFO Building project.
INFO Writing project to RAM on bishop (42.496 kB)...
INFO Deployed.
INFO Running index.js...
Old module firmware detected. Updating...
[Error: Unable to update firmware: Programming confirmation not received.]

[rwaldron]

I will open a new issue