diff options
author | Bluebie <a@creativepony.com> | 2013-12-17 19:49:22 +1100 |
---|---|---|
committer | Bluebie <a@creativepony.com> | 2013-12-17 19:49:22 +1100 |
commit | 75d9e14fe513d1f04f605bc1159cb9a316e89209 (patch) | |
tree | 9c90c6660b64c7851d7b1c8bb6ea0c05f94e67a4 /commandline | |
parent | 21cc37140b779db39a63ba7747ade08f99513594 (diff) | |
download | micronucleus-75d9e14fe513d1f04f605bc1159cb9a316e89209.tar.gz micronucleus-75d9e14fe513d1f04f605bc1159cb9a316e89209.tar.bz2 micronucleus-75d9e14fe513d1f04f605bc1159cb9a316e89209.zip |
commandline: no functional changes - improved readme info on configuring linux to not require root access, and included udev rules file - thanks @sodabrew!
Diffstat (limited to 'commandline')
-rw-r--r-- | commandline/49-micronucleus.rules | 16 | ||||
-rw-r--r-- | commandline/Readme | 7 |
2 files changed, 20 insertions, 3 deletions
diff --git a/commandline/49-micronucleus.rules b/commandline/49-micronucleus.rules new file mode 100644 index 0000000..bed33d6 --- /dev/null +++ b/commandline/49-micronucleus.rules @@ -0,0 +1,16 @@ +# UDEV Rules for Micronucleus boards including the Digispark. +# This file must be placed at: +# +# /etc/udev/rules.d/49-micronucleus.rules (preferred location) +# or +# /lib/udev/rules.d/49-micronucleus.rules (req'd on some broken systems) +# +# After this file is copied, physically unplug and reconnect the board. +# +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" +# +# If you share your linux system with other users, or just don't like the +# idea of write permission for everybody, you can replace MODE:="0666" with +# OWNER:="yourusername" to create the device owned by you, or with +# GROUP:="somegroupname" and mange access using standard unix groups. diff --git a/commandline/Readme b/commandline/Readme index 00e91f7..1781e36 100644 --- a/commandline/Readme +++ b/commandline/Readme @@ -12,9 +12,10 @@ Usage on Mac: Usage on Windows micronucleus.exe --run name_of_the_file.hex -Raw binary file writing hasn't been tested much yet and is suspected to not -work. +Raw binary file writing hasn't been tested as much as hex files. Every now and then the program fails once it reaches the Writing stage - this is a known bug - but if you simply rerun the micronucleus command immediately, it -will succeed the second time usually. Most of the time this issue is not present.
\ No newline at end of file +will succeed the second time usually. Most of the time this issue is not present. + +To linux users: sudo is used above because the default configuration under most modern linux distributions is to not allow userspace apps to communicate directly to unknown USB devices. You can fix this by installing some config files, or you can just use sudo. Either way you're going to need root. To configure your system to allow micronucleus access from non-root users, copy 49-micronucleus.rules from this folder to /etc/udev/rules.d/ |