Is the IP address you are using the correct one? To check this, you can start a Terminal Session using screen and then ask for the IP address of the board:
In MAC terminal (please check the right tty.usbserial port):
screen /dev/tty.usbserial-XXXX 115200
Then you can check the IP Address by running:
The IP address you must use is the one next to wlp1s0 where it says "inet addr:" You will see something like:
wlp1s0 Link encap:Ethernet HWaddr
inet addr:192.168.XX.XXX Bcast:192.168.10.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1128 errors:0 dropped:0 overruns:0 frame:0
TX packets:172 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:172497 (168.4 KiB) TX bytes:31199 (30.4 KiB)
Also, which image are you using on your Galileo Board?
screen /dev/tty.usbserial-121 115200
I received next messages: "No such files in directory"
Where can I get "XXXX" for this expression "screen /dev/tty.usbserial-XXXX 115200"?
In order to start a session with screen you need a Serial Cable, when you connect this kind of cable you have to see something like: /dev/cu.usbserial-XXXXXX in the XDK.
For example, look at these images:
You can see that there are two ports related to the board:
/dev/cu.usbserial-A603UZL3 : Port with the Serial Cable
/dev/cu.usbmodem1411: Port with the USB Client connected
The XXX I mentioned before was an example because as you can see the number can vary. And for using screen you need to go to the terminal of your PC and run the command: sudo screen /dev/tty.usbserial-A603UZL3 115200
Are you able to see the device after typing in the terminal of your PC terminal: ls /dev?
What kind of cable are you using? Does the cable use 3.3V or 5V as reference?
Are you using the IoT image?
I don't use Iot image.
I use the 6 pin Serial to Type A USB cable (FTDI cable # TTL-232R-) and after puting expression
screen /dev/tty.usbserial-AI02DVQ7 115200
into Terminal, I'd got this "Sorry, could not find PTY"
Can you help me, please?
In your terminal, run the command ps, then you should see a process related to that port with an identification number.
Now, you need to kill the process with kill + PID, for example if the process has the number 401 you need to enter: kill 401. You can also try with unplugging and plugging the USB cable. Try with those and let me know the outcome.