Intermec CK30

Customizing Your Configuration—Chapter 5
255TE 2000
 5250 Terminal Emulation Programmer’s Guide
S –o<filename>
<filename> is the Intel-hex output file name.
S –v<number>
<number> indicates “ver bosity.” Default: 0, meaning no information ap-
pears on the standard output device. Intermec recommends a value of 1 to
generate a report of where each file is located. You can use higher v al-
ues, but they may not produce useful information f or the end user.
S –a
This option tells FLSNCONV to append data files to an existing Intel-
hex file. The hex file must be the first file name on the command line.
The following chart lists FLSHCONV command line arguments.
Terminal -f<h exnum> -e<hexnum> -d<h exnum>
11XX, 256K Flash -f8000 -eC000 -d60
11XX, 512K Flash -f8000 -eFFC0 -d60
17XX, 512K Flash -f8000 -eFFC0 -d60
5928-5948, 384K Flash -f9000 -eE000 -d60
Locating and Appending .EXE Files
As an example, suppose you are building a customized version of the
17XX Flash program FWP170H0.HEX. As a minimum, you must hav e
the following files:
S 1700BIOS.EXE 17XX BIOS program
S KERNEL.EXE Intermec multitasking services
S FWP170H0.EXE 17XX 5250 TE program
S NORAND.FNT Display character font file. This may be the
standard font file or a customized user
replacement.
S CFGLIT.DAT Terminal literal file. This may be the standard
literal file or a customized user replacement.
To bind these files into an Intel-hex file that is ready for download to a
17XX, use the following single command line to build a file called
NEW.HEX:
flshconv -f8000 -effcO -d60 1700bios.exe kernel.exe
fwp170h0.exe norand.fnt cfglit.dat -onew.hex
Or, you can create a file that contains each file name on a separate line.
Assuming that file was named 1700FILE.LST, use the following command
line for the same results:
flshconv -f8000 -effc0 -d60 @1700file.lst