Microcom 326M User Guide - Manual (Page 52)

Maintenance and Adjustments Chapter 6
40
326M User’s Guide
6.9.1 Compressed File Update
This method is used to update the firmware stored in flash memory. To update the printer’s
firmware the following are required: a compressed MCB or MCA (ZIP file), a host computer
equipped with a RS-232 serial port, and a Terminal Emulation Program (i.e., HyperAccess,
HyperTerminal, Procomm Plus, Tera Term Pro...). The printer is configured at the factory
with serial parameters of 9600,n, 8,1 and the terminal emulation program will need the serial
parameters set to 9600,n, 8, 1.
It is a good idea to completely read through the procedure before an update attempt is
made. Do not send any unnecessary characters or remove the printer’s power during the
update or the printer may become inoperable. Refer to section 6.9.2 in the event the printer
does not function properly after an update and the printer has become inoperable.
1. Make sure the RS-232 serial connection is made between the host and the printer
including the proper Baud rate.
2. It is recommended to use the fastest Baud rate up to 115200 to reduce transfer time.
Refer to the “^D670)” command regarding the printer’s serial port parameters. If the
printer does not update properly, use a slower Baud rate to transfer the update.
3. Contact the Microcom Corporation support department and/or visit the following web
address www.microcomcorp.com to acquire the desired MCA or MCB file.
4.
Issue the “^D945)?” command and retain the resulting listing for comparison after
flash update.
5. Send the MCA or MCB file to the printer in compressed form (ZIP). The MCA must
be updated before the MCB if both are being updated. Failure to do this may cause
the printer to become unstable.
6. After the printer has identified the MCA file, the following dialog will be reported to the
host: “ File received. Unzipping. Please Wait… ” This dialog is only reported if the printer is
set to use the VERBOSE response set. Refer to the “^D550)” command for
additional information regarding the printer response sets.
7. After the file has been unzipped and the checksum verified, the following dialog is
reported to the host: “
Unzipped. CRC Okay: 0x36410D55
” (The checksum shown is for
demonstration purposes only. The checksum will reflect the MCA files internal
checksum and report any differences automatically.) This dialog is only reported if
the printer is set to use the VERBOSE response set. Refer to the “^D550)” command
for additional information regarding the printer response sets.
8. Sample MCA update dialog is reported to the host and is listed below. If the MCB
code is being updated, the same dialog format would be reported with the word
“application” being changed to “bootloader” as the only difference.