Author Topic: Abort Mission, -1 error  (Read 24949 times)

MoFoQ

  • Newbie
  • *
  • Posts: 12
Abort Mission, -1 error
« on: December 31, 2012, 03:46:57 pm »
Originally, I too had the res >= 4 issue (which was solved with udev rules listed here; on a side-note, I think it should be placed in the "Connecting" tutorial).
Anyways, now I get the dreaded "Abort mission! -1 error has occured ..."


Binary sketch size: 756 bytes (of a 6,010 byte maximum)
Running Digispark Uploader...
Plug in device now...
> Please plug in the device ...
> Press CTRL+C to terminate the program.
> Device is found!
connecting: 40% complete
> Device looks like ATtiny85!
> Available space for user application: 6010 bytes
> Suggested sleep time between sending pages: 8ms
> Whole page count: 94
> Erase function sleep duration: 752ms
parsing: 60% complete
> Erasing the memory ...
erasing: 79% complete
>> Abort mission! -1 error has occured ...
>> Please unplug the device and restart the program.


I've tried 6 different sparks and 2 different direct USB ports (not off a hub).
I'll try it on Windows in a bit.

Any thoughts/ideas?
« Last Edit: December 31, 2012, 03:46:57 pm by MoFoQ »

willscott

  • Newbie
  • *
  • Posts: 10
Abort Mission, -1 error
« Reply #1 on: December 31, 2012, 04:29:22 pm »
I also get this.  For me, the underlying libusb error was -EILSEQ, which it looks like means either there was a timeout, or a bad checksum on the response.

My spark works on my mac, so I\'m pretty sure has something to do with linux & the linux usb driver / libusb setup.

MoFoQ

  • Newbie
  • *
  • Posts: 12
Abort Mission, -1 error
« Reply #2 on: December 31, 2012, 07:18:18 pm »
Hmm...that wasn\'t it either; I thought it might be that I needed to have micronucleus\'s uploader be executed with root privileges after reading the README for it so I edited and recompiled the avr-dummy to use sudo but it didn\'t seem to change anything...still got the error.

probono

  • Newbie
  • *
  • Posts: 17
Abort Mission, -1 error
« Reply #3 on: January 01, 2013, 01:58:47 pm »
With my selfmade Digispark compatible breadboard circuit I got this as well. Had to try about 10 times until it succeeded. Seems like \"something\" (timing? voltage? software?) is not 100% reliable.
« Last Edit: January 01, 2013, 01:59:17 pm by probono »

MoFoQ

  • Newbie
  • *
  • Posts: 12
Abort Mission, -1 error
« Reply #4 on: January 01, 2013, 04:30:13 pm »
It\'s starting to look like it might be an issue with the uploader on Linux as I was able to get it to work just fine under Windows.

Is there a debug version of it so I can post debug results?

probono

  • Newbie
  • *
  • Posts: 17
Abort Mission, -1 error
« Reply #5 on: January 01, 2013, 04:38:38 pm »
I was using Linux as well... Ubuntu 12.10, Quantal Quetzal

digistump

  • Administrator
  • Hero Member
  • *****
  • Posts: 1465
Abort Mission, -1 error
« Reply #6 on: January 01, 2013, 07:18:33 pm »
@MoFoQ - you can try an upload of the either of the hex files in the micronucleus repository using just the micronucleus command line app: https://github.com/Bluebie/micronucleus-t85/tree/master/commandline

That might help you debug, and then you can compile the commandline app with any options you\'d like.

For the record this works for me on 12.04 Ubuntu - but I won\'t claim to be a linux expert and would appreciate anything you or anyone else discovers.


Macjbraun

  • Newbie
  • *
  • Posts: 6
Abort Mission, -1 error
« Reply #7 on: January 02, 2013, 03:56:39 pm »
Try with a hub with no other USB devices plugged in the hub. Worked for me.

MoFoQ

  • Newbie
  • *
  • Posts: 12
Abort Mission, -1 error
« Reply #8 on: January 03, 2013, 12:23:06 pm »
@digistump, are you referring to \"cdc232.hex\" and \"littleWire_v11.hex\"?

note, I\'m using 10.04 LTS on this machine, 12.04 on another.
And it doesn\'t seem to like using a USB hub (it doesn\'t even detect it being inserted)

digistump

  • Administrator
  • Hero Member
  • *****
  • Posts: 1465
Abort Mission, -1 error
« Reply #9 on: January 03, 2013, 12:51:38 pm »
@MoFoQ - yes those or any other hex file- basically I\'m just suggesting that you try using micronucleaus directly so you can test with it directly instead of through the Arduino IDE

A few questions:

Is the machine you had it worked successfully on with windows the same machine as one of the linux ones?

Are the linux machines it is not working on laptops or desktops? If desktops have you tried the USB ports on the back with no extension cable?

I\'ll be uploading some linux builds today and I\'ll do a fresh load of 12.04 and see if I can duplicate it (haven\'t been able to duplicate it yet).

Thanks for sticking with me on troubleshooting this!

MoFoQ

  • Newbie
  • *
  • Posts: 12
Abort Mission, -1 error
« Reply #10 on: January 03, 2013, 08:32:24 pm »
it\'s very odd how it works (it might be a permissions thing)

from now on, I will refer to the computers as Computer A and Computer B.
Computer A runs 10.04 only
Computer B runs Win7 and 12.04

Comp A output via micronucleus (non-root):

$ ./micronucleus --run cdc232.hex
> Please plug in the device ...
> Press CTRL+C to terminate the program.
> Device is found!
connecting: 33% complete
> Device looks like ATtiny85!
> Available space for user application: 6010 bytes
> Suggested sleep time between sending pages: 8ms
> Whole page count: 94
> Erase function sleep duration: 752ms
parsing: 50% complete
> Erasing the memory ...
erasing: 66% complete
>> Abort mission! -1 error has occured ...
>> Please unplug the device and restart the program.


Comp A output via micronucleus (root):

# ./micronucleus --run cdc232.hex
> Please plug in the device ...
> Press CTRL+C to terminate the program.
> Device is found!
connecting: 33% complete
> Device looks like ATtiny85!
> Available space for user application: 6010 bytes
> Suggested sleep time between sending pages: 8ms
> Whole page count: 94
> Erase function sleep duration: 752ms
parsing: 50% complete
> Erasing the memory ...
erasing: 66% complete
>> Abort mission! -1 error has occured ...
>> Please unplug the device and restart the program.


Comp B (12.04) output from arduino IDE (non-root):

Running Digispark Uploader...
Plug in device now...
> Please plug in the device ...
> Press CTRL+C to terminate the program.
> Device is found!
connecting: 40% complete
> Device looks like ATtiny85!
> Available space for user application: 6010 bytes
> Suggested sleep time between sending pages: 8ms
> Whole page count: 94
> Erase function sleep duration: 752ms
parsing: 60% complete
> Erasing the memory ...
erasing: 80% complete
> Starting to upload ...
writing: 80% complete
>> Abort mission! An error has occured ...
>> Please unplug the device and restart the program.


Comp B (12.04) output from arduino IDE (root):

Running Digispark Uploader...
Plug in device now...
> Please plug in the device ...
> Press CTRL+C to terminate the program.
> Device is found!
connecting: 40% complete
> Device looks like ATtiny85!
> Available space for user application: 6010 bytes
> Suggested sleep time between sending pages: 8ms
> Whole page count: 94
> Erase function sleep duration: 752ms
parsing: 60% complete
> Erasing the memory ...
erasing: 80% complete
> Starting to upload ...
writing: 100% complete
>> Micronucleus done. Thank you!


Comp B (12.04) output from micronucleus (non-root):

$ ./micronucleus --run cdc232.hex
> Please plug in the device ...
> Press CTRL+C to terminate the program.
> Device is found!
connecting: 33% complete
> Device looks like ATtiny85!
> Available space for user application: 6010 bytes
> Suggested sleep time between sending pages: 8ms
> Whole page count: 94
> Erase function sleep duration: 752ms
parsing: 50% complete
> Erasing the memory ...
erasing: 66% complete
> Starting to upload ...
writing: 83% complete
> Starting the user app ...
running: 100% complete
>> Micronucleus done. Thank you!


Comp B (12.04) output from micronucleus (root):

# ./micronucleus --run cdc232.hex
> Please plug in the device ...
> Press CTRL+C to terminate the program.
> Device is found!
connecting: 33% complete
> Device looks like ATtiny85!
> Available space for user application: 6010 bytes
> Suggested sleep time between sending pages: 8ms
> Whole page count: 94
> Erase function sleep duration: 752ms
parsing: 50% complete
> Erasing the memory ...
erasing: 66% complete
> Starting to upload ...
writing: 83% complete
> Starting the user app ...
running: 100% complete
>> Micronucleus done. Thank you!


Comp B (12.04) summary:
arduino IDE (non-root): FAIL
arduino IDE (root): PASS
micronucleus (non-root): PASS
micronucleus (root): PASS
« Last Edit: January 03, 2013, 08:33:19 pm by MoFoQ »

MoFoQ

  • Newbie
  • *
  • Posts: 12
Abort Mission, -1 error
« Reply #11 on: January 03, 2013, 08:36:06 pm »
forgot to answer your questions about laptops and desktops.

Comp A is a desktop and I used the direct USB ports as well (front, back, etc.)

Comp B is a laptop.
I haven\'t had any issues under Windows 7 and under linux, it looks like micronucleus doesn\'t have an issue.
(though I did notice that if I used \"660\" as listed in the \"res > = 4\" fix, it would not detect insertion; I use \"666\" instead...yes...dreadfully evil :D )

Emerica

  • Newbie
  • *
  • Posts: 4
Abort Mission, -1 error
« Reply #12 on: January 03, 2013, 08:39:14 pm »
Having this problem as well.
I\'ve tried multiple ports directly, through some extensions. 3 sparks.
Into a usb3 hub plugged into a usb2 port was a no go at all.
Ubuntu 12.04

Running Digispark Uploader...
Plug in device now...
> Please plug in the device ...
> Press CTRL+C to terminate the program.
> Device is found!
connecting: 20% complete
connecting: 23% complete
connecting: 27% complete
connecting: 30% complete
connecting: 34% complete
connecting: 40% complete
> Device looks like ATtiny85!
> Available space for user application: 6010 bytes
> Suggested sleep time between sending pages: 8ms
> Whole page count: 94
> Erase function sleep duration: 752ms
parsing: 40% complete
parsing: 60% complete
> Erasing the memory ...
erasing: 60% complete
erasing: 60% complete
[---------------------60 to 79%-----------------------]
erasing: 79% complete
>> Abort mission! -1 error has occured ...
>> Please unplug the device and restart the program.

digistump

  • Administrator
  • Hero Member
  • *****
  • Posts: 1465
Abort Mission, -1 error
« Reply #13 on: January 03, 2013, 08:56:15 pm »
@Emerica - have you tried running it as root?

Emerica

  • Newbie
  • *
  • Posts: 4
Abort Mission, -1 error
« Reply #14 on: January 03, 2013, 09:08:39 pm »
Yes, same deal. Either using sudo or sudo su and then trying, no go.
Followed the guide as well as:
/etc/udev/rules.d/49-digispark.rules
SUBSYSTEMS==\"usb\", ATTRS{idVendor}==\"16d0\", ATTRS{idProduct}==\"0753\", MODE:=\"0666\"
KERNEL==\"ttyACM*\", ATTRS{idVendor}==\"16d0\", ATTRS{idProduct}==\"0753\", MODE:=\"0666\", ENV{ID_MM_DEVICE_IGNORE}=\"1\"