![]() Where udev-diag is essentially: env >/tmp/udev-eventsįor more general use, the udevmonitor program is also handy. Incidentally, for diagnostics I sometimes run the following rule, to get an idea of what the udev scripts are seeing: RUN+="/home/me/bin/udev-diag. Tested successfully with PuTTY on my own serial dongle. This rule will create a symlink to whichever /dev/ttyUSB* happens to be assigned to your device. A few steps later it will load the device's specific driver, and since this is a serial device, it will engage the tty subsystem, which creates a device file that PuTTY can use. ![]() Since it's a USB device, it first engages the usb subsystem, which I think will create a raw USB device, which PuTTY can't use. 3.3 After both putty applications are started, send a byte. SUBSYSTEM="usb", ATTRS="ea60", SYMLINK+="serial"Ī USB device generates several udev events when you plug it in as the kernel recognizes more things about it. 3.1 Start putty windows version and connect to another virtual COM port (in my case it is COM4). I have rebooted since I last modified it. ![]() I'm using a udev rule to give it a special name. I need to access one of them in particular. The port number may be different in your computer. The port number is COM4 in below example. Enter the port number inside 'Serial line to connect to' text box. I have multiple USB-to-serial converters. 1) After downloading PuTTY, connect the console cable with Cisco Router or Swtich, double click putty.exe to execute it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |