So far as default settings go on the integrated UARTs of a TX2, this is always speed 115200, 8 bits, no parity, and one stop bit. I don’t know with your particular (CH341) UART, but consider that there are always two UARTs involved even if each end only sees one UART. If a UART at either end has the wrong parity or stop bits, then the data won’t be interpreted correctly. The other half of the UART connection is the one in the actual GPS. It does not hurt to try, and there wouldn’t be any damage if settings differ, so it is ok to experiment (two UART connections have to be matching voltage levels, but software settings cause no harm when wrong…they just won’t work as expected).
What you’d want to do is see if you can find the documentation for the GPS itself, and see if serial UART settings can be changed or not. I recall seeing some GPS units in the past that have a fixed UART setting and the other UART is forced to match the GPS’s UART. If that is the case, you’d be able to find documentation on either how to change the GPS’s UART settings, or else the setting for your (CH341) UART which would match the GPS. Should your terminal and the GPS be confirmed to have matching settings, then probably the data you see is correct and it is only how the characters are being displayed which is unusual. On the other hand, if for example stop bits are wrong, then the data is shifting by a byte and showing some control characters as data instead of using it as a control sequence.
FYI, much of what is showing up could be shown as white space or be used as a delimiter between packets. Take something like the
0x13 character…this is a carriage return. Depending on what operating system you are on, this would be interpreted as hitting the “enter” key during typing. Seeing the cursor go to a new line, and seeing hex
0x13, are just two valid different ways of seeing that character. Your serial terminal itself might be doing that. A terminal application on a Mac might view such characters differently than a Windows application, and this would also differ from a Linux application on how it displays. Should all your settings match between GPS and your USB UART, then I’d think it is really not an error to see this, but is instead a choice of the application choosing to show hex instead of interpreting this as white space.