Include a udev rules file for v1 boards too, for permissions
authorKarl Palsson <karlp@tweak.net.au>
Fri, 4 Nov 2011 02:30:13 +0000 (02:30 +0000)
committerKarl Palsson <karlp@tweak.net.au>
Fri, 4 Nov 2011 02:30:13 +0000 (02:30 +0000)
49-stlinkv1.rules [new file with mode: 0644]
README

diff --git a/49-stlinkv1.rules b/49-stlinkv1.rules
new file mode 100644 (file)
index 0000000..d474d6a
--- /dev/null
@@ -0,0 +1,11 @@
+# stm32 discovery boards, with onboard st/linkv1
+# ie, STM32VL
+
+SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3744", \
+    MODE:="0666", \
+    SYMLINK+="stlinkv1_%n"
+
+# 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/README b/README
index 109aa25003a298fffa36e4e4412823ff98ef42dd..470c52a5977741d648e0660201dd417efe74116b 100644 (file)
--- a/README
+++ b/README
@@ -75,13 +75,13 @@ for GDB.
 Setting up udev rules
 =====================
 
-For convenience, you may install udev rules file, 49-stlinkv2.rules, located
+For convenience, you may install udev rules file, 49-stlinkv*.rules, located
 in the root of repository. You will need to copy it to /etc/udev/rules.d,
 and then either reboot or execute
 $ udevadm control --reload-rules
 
-Udev will now create a /dev/stlinkv2_XX file, with the appropriate permissions.
-This is currently all the device is for, (only one stlinkv2 is supported at 
+Udev will now create a /dev/stlinkv2_XX or /dev/stlinkv1_XX file, with the appropriate permissions.
+This is currently all the device is for, (only one stlink of each version is supported at 
 any time presently)
 
 Running programs from SRAM