Closed rin67630 closed 11 months ago
Hi I am afraid this issue has nothing to do with the RPi distro. It was the Java development that was not supporting Bullseye any more.
Hi I am afraid this issue has nothing to do with the RPi distro. It was the Java development that was not supporting Bullseye any more. Sorry.
Hi, i have been using Raspberry Pis since ages combined with ESP modules to make the preprocessing. On the Raspberry * side, I use a Java application that reads data from the /dev/ttyUSB0 or /dev/ttyUSB1 ports using ser2net.
Since an upgrade a week ago from within Bullseye 32bit, the /dev/ttyUSB0 seems to get inaccessible over ser2net.
I have repeated with a fresh vanilla installation of Bullseye: exactly the same behavior, ser2net does not see the /dev/ttyUSB0 port. Another test: dmesg | grep tty shows very well the port /dev/ttyUSB0 driven by a CH340 as available.
Then I did a fresh vanilla installation of Buster and everything runs like a charm.
Has someone heard about issues with the serial ports /dev/ttyUSB0 (1) together with the last upgrade of Bullseye 32bit and ser2net?
My hardware: Raspberry Pi 3A or Raspberry Pi 3B and an ESP8266 connected over USB. My Software: a specific development in Java reading the port /dev/ttyUSBx through ser2net as a proxy.