- #What is the difference between teraterm and teraterm pro serial#
- #What is the difference between teraterm and teraterm pro update#
- #What is the difference between teraterm and teraterm pro Patch#
#What is the difference between teraterm and teraterm pro serial#
No way to do Xmodem, etc - this old machine was designed to receive serial data from a teletype and no hand-shaking. I have attempted to use this version of TeraTerm to download the binary diagnostic files to the PDP-8. The old Digital Equipment Corporation had diagnostic programs to load onto the machine and test the hardware. I am trying to restore a 1970's PDP-8f computer with 4k of ferrite core memory (althoughI have made a solid state memory for initial testing purposes). I am a hobbyist who is weak on software but a bit better at hardware.
There also appears to be some kind of Bugzilla like ticket system on that site too. If there is a fault you might want to look at the SVN revision history and see when and how it was broken in the first place.
#What is the difference between teraterm and teraterm pro Patch#
I'm sure "zmatsuo" would love a patch sent back to him if you can fix a fault in the open source (the whole point of FOSS software!)
Also then follow the actual transfer and watch for the stopping condition. This would be best explored by loading the SLN into VisualStudio, build for "Debug" and then breakpoint around there - start a file transfer and see if it hits a breakpoint there and see what result it actually reads for file size. It's quite tricky to follow the source as the filenames are a bit cryptic (maybe because of Japanese heritage?) but I *think* the file transfer stuff is in the region of line 1194 in this:Īnd it looks like line 1203 may be where it reads the size of the file to send. So apparently Tera Term's binary file transfer is not working properly! Has any one else seen this problem? I searched for any similar reports but could not find any. I tried RealTerm which does indeed send the correct number of bytes: However when I send the file with "binary" option checkbox unchecked I get almost correct number of bytes - this is expected since Tera Term modifies new-line and some control characters (which of course is disastrous for my firmware so cannot be used). RX count = 18432 bytes (and goes on forever) RX count = 1024 bytes <- pressed MCU reset button RX count = 57344 bytes <- pressed MCU reset button Here is the output with a slightly modified boot loader that just prints number of received bytes every 1kB boundary: But for some reason Tera Term will keep on sending data indefinitely even though the file size is only 7724 bytes!
#What is the difference between teraterm and teraterm pro update#
My boot loader (named "BOOTNPB" as in no-protocol binary) uses a simple text-based interface with commands being single-characters (e = erase, l = load firmware, s = start firmware). When I want to update FW I press "l" and then simply send the binary file to the boot loader through UART using Tera Term's File -> Send file. While working on my custom boot loader I stumbled upon this weird issue with Tera Term 4.105.
0 kommentar(er)
