-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[C64] Garbage characters when using UP2400 #37
Comments
I haven't made any changes to up2400 from its original repo. |
it is important that RTS/CTS handshaking be set up, also, the modem needs to not escape 0xFF as 0xFF 0xFF (treat as raw). |
Thanks; I'll double-check. I've only been able to try this under emulation with Looks like the UP2400 driver change was committed by @greg-king5 in f270f52
|
If you use tcpser, PLEASE USE MY FORK, which has the IAC escaping code excised: http://github.com/tschak909/tcpser and run tcpser with -i "&K3" -Thom |
That seems to have done the trick, thanks! Seems that these days everyone has their own tcpser fork! It's hard to keep track of all of them! |
Three points about VICE:
|
I've noticed that when using the UP2400 driver, screens will often have garbage characters in places, and incorrectly-drawn or positioned, or sometimes completely missing elements - see the screenshot below.
This doesn't seem to be a protocol-decoding issue, since the same screens render fine with SwiftLink, but they always seem to render with the same corruption under UP2400. Could this be related to #28, discussing a change in the upstream UP2400 driver to fix an issue where
0x00
bytes got received as0x0D
? From commit f270f52, it looks like the the UP2400 driver distributed with PlatoTerm has diverged from that codebase, but I couldn't find a copy of the source to examine the changes.The text was updated successfully, but these errors were encountered: