aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJosh Rahm <joshuarahm@gmail.com>2023-01-18 23:30:45 -0700
committerJosh Rahm <joshuarahm@gmail.com>2023-01-18 23:30:45 -0700
commit60228468ff989f26fb4f9e0ae43bd0d19cff84d7 (patch)
tree70ce68250c9376e79c8be8086e4d5bb0e7d60aa3
parentd93ca841f64cfe6a5ddcb45510becadd83358d84 (diff)
downloadch573-60228468ff989f26fb4f9e0ae43bd0d19cff84d7.tar.gz
ch573-60228468ff989f26fb4f9e0ae43bd0d19cff84d7.tar.bz2
ch573-60228468ff989f26fb4f9e0ae43bd0d19cff84d7.zip
more in the readme
-rw-r--r--ch-flash/README.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/ch-flash/README.md b/ch-flash/README.md
index 6fcf010..640f961 100644
--- a/ch-flash/README.md
+++ b/ch-flash/README.md
@@ -13,3 +13,18 @@ machine.
With this new utility one can run the flash program and then connect the device
when it will be flashed.
+
+## udev
+
+To flash the device requires some permissions to set up. One can run this flash
+program as root to flash the device, but for those who wish to keep the flashing
+under-privliged, one can add the following udev rules in
+`/etc/udev/rules.d/50-ch573.rules`:
+
+```
+SUBSYSTEM=="usb", ATTR{idVendor}=="4348", ATTR{idProduct}=="55e0", MODE:="0666"
+```
+
+Then run the command:
+
+`udevadm control --reload-rules`