
81/84
ST63E85, T85 ST63E87, T87
3 GENERAL INFORMATION
3.1 ORDERING INFORMATION
The following chapter deals with the procedure for
transfer the Program/Data ROM codes to SGS-
THOMSON.
Communication of the ROM Codes. To commu-
nicate the contents of Program/Data ROM memo-
ries to SGS-THOMSON, the customer must send:
– one file in INTEL INTELLEC 8/MDS FORMAT
(either as an EPROM or as a MS-DOS diskette)
for the PROGRAM Memory;
– one file in INTEL INTELLEC 8/MDS FORMAT
(either as an EPROM or as a MS-DOS diskette)
for the EEPROM initial content (this file is option-
al).
The program ROM should respect the ROM Mem-
ory Map as in Table 4.
The ROM code must be generated with an ST6
assembler. Before programming the EPROM, the
EPROM programmer buffer must be filled with
FFh.
For shipment to SGS-THOMSON, the master
EPROMs should be placed in a conductive IC car-
rier and packed carefully.
3.2 CUSTOMER EEPROM INITIAL CONTENTS:
FORMAT
a. The content should be written into an INTEL
INTELLEC format file.
b In the case of 384 bytes of EEPROM, the start-
ing address is 000h and the end address is
7Fh. The order of the pages (64 bytes each) is
an in the specification (i.e. b7, b1 b0: 001, 010,
011, 101, 110. 111).
c. Undefined or don't care bytes should have the
content FFh.
3.3 OSD TEST CHARACTER
IN ORDER TO ALLOW THE TESTING OF THE
ON-CHIP OSD MACROCELL THE FOLLOWING
CHARACTER MUST BE PROVIDED AT THE
FIXED 3Fh (63) POSITION OF THE SECOND
OSD BANK.
Listing
Generation
&
Verification.
When
SGS-THOMSON receives the files, a computer
listing is generated from them. This listing refers
extractly to the mask that will be used to produce
the microcontroller. Then the listing is returned to
the customer that must thoroughly check, com-
plete, sign and return it to SGS-THOMSON. The
signed list constitutes a part of the contractual
agreement for the creation of the customer mask.
SGS-THOMSON sales organization will provide
detailed information on contractual points.
Figure 5. OSD Test Character