Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 8015

Interfacing (DSI, CSI, I2C, etc.) • Re: serial port clarification

$
0
0
I finally got GPS to work on a 3B+. now I have a few questions

You have to shut down the console to use the serial port for GPS. does this prevent logging in via SSH?

No. ssh uses your network not your UART.
does assigning the serial port to GPS prevent the use of the Arduino IDE?

Can't say for certain but unless you're using the serial port to connect to the arduino they answer is likely to be no.
ls /dev/serial* returns /dev/serial0 and /dev/serial1. GPS is on serial0. cgps and gpsmon both show GPS data. cat /dev/serialo returns "device is busy". of course the device is busy, that is the point of entering cat /dev/serialo.

Not sure I understand your point here, but yes, it can.

/dev/serial0 is a symbolic link to the actual serial device. It's there for user convenience as the actual UART routed to the GPIO header varies depending on whether the Bluetooth hardware is enabled and which UART it is using. You can see which "real" UART it is using by

Code:

ls -l /dev/serial?
I tried a couple of simple GPS Python programs. one gets data from serial0, the other gets data from gpsd(get). both bail and fail because serial0 is busy. what do you have to do to get this thing to understand that what I need is to see what it is doing while it's busy?

Sorry, can't help with that.

Statistics: Posted by thagrol — Sun Aug 17, 2025 1:54 pm



Viewing all articles
Browse latest Browse all 8015

Trending Articles