Tera Term Xmodem Download
Mozell Rhule
I have installed TeraTerm's latest version on my Windows PC. I was reading the help menu of the TeraTerm and they reference the 'xmodemsend' command to transfer a file over Xmodem protocol via command line. I searched my TeraTerm directory for this command but can't seem to find it. What am I missing here?
Basically, my question is how exactly the xmodemsend command should be implemented. I read Tera Terms index file that has the list and explanation of all the commands, but for whatever reason it's not working
The macro is getting hung up on the line 'wait 'power!'', but I'm using a program to monitor the serial port's data transfer and after the transmitter replies to the xmodem receive signal, the computer never sends the file.
Tera Term is Tera Term Pro 2.3 succession version and is being officially recognized by the original author. Tera Term is open source free software terminal emulator supporting UTF-8 protocol.Now TTSSH supports SSH2 protocol (Original version supports SSH1).
I have a similar issue with LabWindows/CVI Xmodem where the receiving device sends 'CAN' and terminates the transfer (likely due to an overrun error). The issue is unrelated to baud rate as it occurs at 9600 and 115200 bps. The file can be uploaded sucessfully using Hyperterminal. Transfering a file to a different device using the same CVI function also works fine. I used Portmon to capture the port traffic as you recommended. What is interesting is that when Portmon is active, the CVI Xmodem transfer always works fine (but fails when Portmon is not running). It appears that the extra delay (introduced between each byte) allows for a sucessfull transfer. How is this delay time (between bytes) set in the LabWindows/CVI Xmodem function?
Configure the terminal emulator program for a data rate of 115200 bps to match the xmodem speed specified above. To do this close the previous terminal session of 9600 bps and open a new one at 115200 with 8-N-1. The trick here is that the Cisco 1603 only supports a maximum baud rate of 9600 bps. Therefore, when connected at 115200 bps, you cannot see the router prompt. This is an important point to remember. Once connected to the router at 115200 bps, select Transfer and Send File from the HyperTerminal menu bar.
Once the router boots up in ROMmon, the HyperTerminal sessions start to display illegible characters. You need to exit the current terminal session and start a new one at a data rate of 115200 bps to match the console rate as in Step 2.
The standard procedure uses the default console speed of 9600 bits per second. Xmodem is a slow transfer protocol, and the transfer of a file as large as a Cisco IOS software image could take an long time. An increase to the console speed on the 3600 router helps decrease the time it takes to do the xmodem file transfer.
3. After the hyperterminal is set, you receive a rommon prompt. Enter the xmodem command. Before you enter an xmodem command, there must be a software image that resides in your terminal or your local hard drive.
This made me think of how to recover a corrupted IOS image (which you can fine in the tips and tricks link above). Where boot the device in to ROMmon mode, and then copy the IOS over using the xmodem protocol. Almost all the mainstream terminual emulators have this built in, and while for recovering the IOS you need to increase the baud speed of the console port to speed up the copying process, as the configuration file is only 20-30kb max for most people, the standard speed will move that across in a few seconds.
PPS. Although I prefer the xmodem method, you can improve the reliability of the copy/paste method by increasing the line/character delay in you terminal emulation program. A 5msec delay per character seems to help, although with a 1000+ lines of configuration you may get from a complex configuration, you may find the paste takes a little time, and you may still get errors.
760c119bf3