summaryrefslogtreecommitdiffstats
path: root/commandline/Readme
diff options
context:
space:
mode:
authorcpldcpu <cpldcpu@gmail.com>2013-12-17 10:06:40 +0100
committercpldcpu <cpldcpu@gmail.com>2013-12-17 10:06:40 +0100
commita44f516520527a08c251561b28ee973d4060195f (patch)
tree4ce48f1e6762ffb12816fd7b6cd3c3e62705ef64 /commandline/Readme
parenta6afba324cc7ae49b755a2786104f45aea2b290c (diff)
parent04e0d950d18fba8af17e844f9d6d0bb868cb5981 (diff)
downloadmicronucleus-a44f516520527a08c251561b28ee973d4060195f.tar.gz
micronucleus-a44f516520527a08c251561b28ee973d4060195f.tar.bz2
micronucleus-a44f516520527a08c251561b28ee973d4060195f.zip
v1.10: Merging changes into testing
Diffstat (limited to 'commandline/Readme')
-rw-r--r--commandline/Readme14
1 files changed, 10 insertions, 4 deletions
diff --git a/commandline/Readme b/commandline/Readme
index 00e91f7..329247a 100644
--- a/commandline/Readme
+++ b/commandline/Readme
@@ -6,15 +6,21 @@ three. To make and install, do the regular 'make; sudo make install' on unixes.
On windows just 'make' with mingw and do whatever people do with windows exes.
Usage on Ubuntu:
- sudo micronucleus --run name_of_the_file.hex
+ sudo micronucleus --run name_of_the_file.hex
Usage on Mac:
micronucleus --run name_of_the_file.hex
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/