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

Pushing new code after code is already there crashes tessel #415

Closed
freethan opened this issue Oct 27, 2015 · 4 comments
Closed

Pushing new code after code is already there crashes tessel #415

freethan opened this issue Oct 27, 2015 · 4 comments

Comments

@freethan
Copy link

Hi from #fullstackcon,
we encountered the following error while trying to push new code to a tessel board that was already running some older code:

t2 push index.js 
INFO Looking for your Tessel...
INFO Connected to anykey over USB
INFO Writing index.js to Flash on anykey (3.072 kB)...
INFO Deployed.
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: Error upon remote process exit: 1
    at USBProcess.<anonymous> (/usr/local/lib/node_modules/t2-cli/lib/usb/usb_process.js:49:26)
    at USBProcess.g (events.js:260:16)
    at emitOne (events.js:77:13)
    at USBProcess.emit (events.js:169:7)
    at Parser.<anonymous> (/usr/local/lib/node_modules/t2-cli/lib/usb/usb_daemon.js:121:14)
    at emitOne (events.js:77:13)
    at Parser.emit (events.js:169:7)
    at Parser._write (/usr/local/lib/node_modules/t2-cli/node_modules/usb-daemon-parser/index.js:152:16)
    at doWrite (_stream_writable.js:292:12)
    at writeOrBuffer (_stream_writable.js:278:5)
    at Parser.Writable.write (_stream_writable.js:207:11)
    at ondata (_stream_readable.js:525:20)
    at emitOne (events.js:77:13)
    at emit (events.js:169:7)
    at readableAddChunk (_stream_readable.js:146:16)
    at Readable.push (_stream_readable.js:110:10)
Abort trap: 6

After that the board crashes and we lose connection. We had to reboot it and then do a
t2 erase and then a t2 push index.js

Cheers

@johnnyman727
Copy link
Contributor

Thanks for reporting this issue and the workaround! Will need to fix this asap.

@johnnyman727
Copy link
Contributor

Will be fixed with #516.

@freethan
Copy link
Author

freethan commented Jan 7, 2016

Cheers! Thanks for getting back to me on this.
I have no board with me at this point and won't be able to test it. Should I close the issue?

@johnnyman727
Copy link
Contributor

I got it! Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants