User Tools

Site Tools


digispark:tutorials:linuxtroubleshooting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
digispark:tutorials:linuxtroubleshooting [2014/12/20 23:20]
McLenin [Arch Troubleshooting]
digispark:tutorials:linuxtroubleshooting [2017/12/03 11:41] (current)
Jamezrin [Arch Troubleshooting]
Line 6: Line 6:
 If your sketch uses DigiUSB to communicate with the PC, you need both the legacy 0.1 version of libusb and version 1.0(http://​www.libusb.org/​). ​ For compiling the DigiUSB programs, also ensure the package libusb-compat-devel is installed. If your sketch uses DigiUSB to communicate with the PC, you need both the legacy 0.1 version of libusb and version 1.0(http://​www.libusb.org/​). ​ For compiling the DigiUSB programs, also ensure the package libusb-compat-devel is installed.
  
-====== ​permissions ​======+If you are getting an error (especially on ubuntu) when compiling or uploading sketches - try installing libusb and possibly lib32stdc on linux - (on ubuntu get it by issuing: apt-get install lib32stdc++6) 
 + 
 +====== ​Permissions ​======
  
 Try running Arduino as root. If possible try the whole process as root. Try running Arduino as root. If possible try the whole process as root.
Line 14: Line 16:
 Bad permissions generally cause the "Abort mission! -1 error has occurred ..." error during upload. Bad permissions generally cause the "Abort mission! -1 error has occurred ..." error during upload.
 "​micronucleus:​ library/​micronucleus_lib.c:​63:​ micronucleus_connect:​ Assertion `res >= 4' failed."​ is also a result of bad permissions. "​micronucleus:​ library/​micronucleus_lib.c:​63:​ micronucleus_connect:​ Assertion `res >= 4' failed."​ is also a result of bad permissions.
 +
 ====== Ubuntu Troubleshooting ====== ====== Ubuntu Troubleshooting ======
  
Line 22: Line 25:
 Ubuntu and other modern Linux distibutions use udev to manage device files when USB devices are added and removed. By default, udev will create a device with read-only permission which will not allow to you download code. You must place the udev rules below into a file named /​etc/​udev/​rules.d/​49-micronucleus.rules Ubuntu and other modern Linux distibutions use udev to manage device files when USB devices are added and removed. By default, udev will create a device with read-only permission which will not allow to you download code. You must place the udev rules below into a file named /​etc/​udev/​rules.d/​49-micronucleus.rules
  
-These rules are adapted from those used for Teensy boards, maintained [here](http://​www.pjrc.com/​teensy/​49-teensy.rules)+These rules are adapted from those used for Teensy boards, maintained ​by [[http://​www.pjrc.com/​teensy/​49-teensy.rules|PJRC]]
  
 <​code>​ <​code>​
Line 42: Line 45:
 # GROUP:​="​somegroupname"​ and mange access using standard unix groups. # GROUP:​="​somegroupname"​ and mange access using standard unix groups.
 </​code>​ </​code>​
 +
 +Perhaps it's necessary to reload the rules as root.
 +
 +<​code>​udevadm control --reload-rules</​code>​
  
 ====== Arch Troubleshooting ====== ====== Arch Troubleshooting ======
  
-The AUR arduino package will not work since it is version 1.0.6! You need to install 1.5.8 from the [Arduino page](http://​arduino.cc/​download.php?​f=/​arduino-1.5.8-linux64.tgzor if you have a [32 bit system](http://​arduino.cc/​download.php?​f=/​arduino-1.5.8-linux32.tgz)+The AUR arduino package will not work since it is version 1.0.6! You need to install 1.5.8 from the [[http://​arduino.cc/​download.php?​f=/​arduino-1.5.8-linux64.tgz|Arduino page]] ​or if you have a [[http://​arduino.cc/​download.php?​f=/​arduino-1.5.8-linux32.tgz|32 bit system]]
  
 You will also need the latest Digispark files that you can get by:  You will also need the latest Digispark files that you can get by: 
Line 64: Line 71:
 </​code>​ </​code>​
  
-The last part is getting the micronucleus to work. For this (at least on 64 bit systems), ​compiling is the only option+The last part is getting the micronucleus to work. For this (at least on 64 bit systems), ​you can install ​the AUR package [[https://​aur.archlinux.org/​packages/​micronucleus-git/​|micronucleus-git]] or compile it yourself.
  
 <​code>​ <​code>​
digispark/tutorials/linuxtroubleshooting.1419146418.txt.gz · Last modified: 2014/12/20 23:20 by McLenin