Closed rFond closed 7 months ago
Good catch! Do you want to write this fix as patch, or should we?
I'm happy for you to do it. I'm not very comfortable with Git. Thank's
git clone ...
git checkout -b ttyX30-fix
(or whatever name you want to choose for the branchgit commit -asv
git push origin ttyX30-fix
That's a rough plan, and I probably forgot some detail now. Drop questions then. And the rest we can sort out in the merge request.
Sorry but I won't be able to correct this problem. I don't have the technical knowledge to do this
No problem, will take over.
It turned out to be more complex: The issue was rooted in the wiring differences between PG1 and PG2 devices, not in the software version. Please give the proposed solution a try.
Hello, with the latest version of Debian (device version FS03), the ttyX30 port no longer exists. To fix the issue, I had to modify the /etc/udev/rules.d/20-create-symbolic-link-for-serial-port.rules file.
The kernel is no longer correct: udevadm info --attribute-walk --path=$(udevadm info --query=path --name=/dev/ttyUSB0)
looking at parent device '/devices/platform/bus@100000/4000000.dwc3/4010000.usb/xhci-hcd.0.auto/usb1/1-1/1-1.4/1-1.4:1.0': KERNELS=="1-1.4:1.0" SUBSYSTEMS=="usb" DRIVERS=="cp210x" ATTRS{authorized}=="1" ATTRS{bAlternateSetting}==" 0" ATTRS{bInterfaceClass}=="ff" ATTRS{bInterfaceNumber}=="00" ATTRS{bInterfaceProtocol}=="00" ATTRS{bInterfaceSubClass}=="00" ATTRS{bNumEndpoints}=="02" ATTRS{supports_autosuspend}=="1"
So in my new file : SUBSYSTEM=="tty", SUBSYSTEMS=="usb", KERNELS=="1-1.4:1.0", DRIVERS=="cp210x", SYMLINK+="ttyX30" SUBSYSTEM=="tty", KERNEL=="ttyS2", DRIVERS=="omap8250", SYMLINK+="ttyX30"