Ymodem initial packet incorrect on send
We've just run into this as well, and needed to add code to our embedded YMODEM implementation to ignore the additional blocks coming in.
123
I see this issue as far back as version 4.86 from 2015.02.28.
The problem comes from the need to start the receiver before navigating File->Transfer->YMODEM->Send, choosing a file, and pressing "Open". By this time, if the receiver has sent multiple "Start" requests TerraTerm will reply to each of them with a copy of the first packet. This will overwhelm many embedded systems.
My solution was to place a longer delay before the first "Start" message to give the user time to navigate through the menus to their file.
In my opinion, the correct solution would be for TerraTerm to flush the input stream at the start of a transfer.
(匿名) への返信
In my opinion, the correct solution would be for TerraTerm to flush the input stream at the start of a transfer.
I have the same opinion as you. If I use macro to transfer without file selection dialog, TeraTerm can transfer normally. TeraTerm should flush the input stream before transfer.
Same problem ticket #39667.
1) Begin a Ymodem download to a embedded system.
2) Wait for the the remote system to send 3-4 0x43('C') characters(it is requesting the download to start) before starting a Ymodem send.
3) Based on the number of 0x43's that TeraTerm has received, it will send a initial file size packet to the remote device that is the incorrect size. This bad packet(more than 133 bytes long) is a correct packet that is duplicated by the amount of 0x43's received. If seven 0x43's were received before the file transfer was started, then the initial packet will have six correct packets lumped into a single bad initial file size packet.
[ 22/08/2017 14:31:36 ] - Close port COM2
[ 22/08/2017 14:31:42 ] - Open port COM2 (C:\Program Files (x86)\teraterm\ttermpro.exe) [ 22/08/2017 14:31:45 ] Read data (COM2) [ 22/08/2017 14:31:48 ] Written data (COM2) [ 22/08/2017 14:31:48 ] Read data (COM2) [ 22/08/2017 14:31:48 ] Written data (COM2) [ 22/08/2017 14:31:48 ] Read data (COM2) [ 22/08/2017 14:31:50 ] Written data (COM2) [ 22/08/2017 14:31:50 ] Read data (COM2) [ 22/08/2017 14:31:55 ] Read data (COM2) [ 22/08/2017 14:32:00 ] Read data (COM2) [ 22/08/2017 14:32:27 ] Read data (COM2) [ 22/08/2017 14:32:27 ] Written data (COM2) [ 22/08/2017 14:32:28 ] Read data (COM2)