Symbol PDT 3400 Series, Product Reference Manual

Page: 84 / 146

6-26
PDT 3400 Product Reference Guide
Sending the Hex Image
Once the hex file is built, you are ready to download it to the PDT 3400. A Hex image
download requires a program loader stored on the PDT 3400 and either TCM or
HEX2TERM running on the development PC. The PDT 3400 comes with a program loading
utility, Initial Program Loader (IPL), stored in write-protected flash. To run IPL, the PDT
3400 must be connected to a host PC by direct serial connection (COM1).
You have the option of creating your own program loader using the Flash API (it does not
replace the IPL). Refer to the PDT 3400 System Software Manual for DOS Applications for
more information on the Flash API.
Loading the BIOS
Uploading a new BIOS erases only the segment of Flash where BIOS is stored. While IPL is
updating the BIOS, the BIOS image is saved in memory until the entire BIOS is received and
verified. The ROM Disk image and application storage area are unaffected.
Loading a ROM Disk
The PDT 3400’s ROM Disk is organized as two separate drives instead of the conventional
hard disk. This separation allows for updating a section without erasing the entire disk.
If ROM Disk 1 (C:) is updated, IPL erases from the specified start of ROM Disk 1 to the end
of Flash ROM, including ROM Disk 2 and user space (application storage). If ROM Disk 2
(D:) is selected, ROM after Disk 1 is erased, including ROM Disk 2 and user space.
Preparing for the Download
Connect the PDT 3400 and Development PC
To send the hex file to the PDT 3400 requires placing the PDT 3400 in a cradle linked to the
development PC. Refer to Chapter 3, Installing the Hardware, for information on connecting
the cradle to the PC.
Setup for Download Using TCM
Note: If you made changes to the script since saving it, save the script again.
1. Select the script so that the script is active in the Script Window.
2. Choose Script | Send from the menu bar.