Hi,
you need to check if the devices are available under /dev/ttyAMA0
if you see them there, I could not really imagine what elso should fail then.
Are you using udev ?
If yes you Need to check: /etc/udev/rules.d/serial-symlinks.rules

BR
Edwin

Hi,

I don't understand very well, but I think that the problem is this:

http://raspberrypi.stackexchange.com/qu ... ect=1&lq=1

But I don't understand what I need to do!

BR

Hi,
yes sounds like this is your problem

could you check how the OS register your device Login by ssh and type:

dmesg | grep -i tty

and as i understand you could give /dev/serial0 a try

BR
Edwin

Hi Edwin,

I solved:

http://raspberrypi.stackexchange.com/qu ... -on-my-pi3

in particolar:

Zitat:
You may also need to disable the serial console. The easiest way to do this is via raspi-config under Advanced Options -> Enable/Disable shell and kernel messages on the serial connection.
If you don't have raspi-config, it doesn't work, and/or you want to double check, first look in /boot/cmdline.txt. If you see:
console=/dev/ttyS0,115200
Or:
console=/dev/serial0,115200
Or anything involving console= that isn't console=tty1, remove it. Make sure not to accidentally add a line break to that file, it should remain all one line with spaces between the options, but no spaces around any =.
The other aspect is the login started by the init system. On Raspbian jessie, check:
ls /etc/systemd/system/getty.target.wants
If you see that serial device node (ttyS0) mentioned, disable this service:
systemctl disable e serial-getty@ttyS0.service e
You will have to reboot for these things to take effect.

I don't know what I done, but it work!