Data I/O UniSite-xpi, User Manual

Page: 281 / 413

6. Translation Formats
UniSite-xpi User Manual 6-43
• The U-field cells are not included in the C (fuse checksum) field.
• The U field reads left to right to be consistent with the L (fuse list) and
E fields.
The syntax for the U field is as follows:
<User Data Fuse List>::’U’<binary-digit(s)>’*’
The character U begins the U field and is followed by one binary digit for
each U fuse. Each binary digit indicates one of two possible states (zero,
specifying a low-resistance link, or one, specifying a high-resistance link)
for each fuse.
For example,
QF24*
L0000
101011000000000000000000*
E10100111*
C011A*
U10110110*
Electrical Data (E field) The E field allows special feature fuses that do not affect the logic
function of the device to be specified in JEDEC files.
The following guidelines apply to the E field:
• The E-field cell must be explicitly provided if the E field is present.
• The F (default fuse state) field does not affect E fuses.
• There can only be one E field in a JEDEC file.
• The E field fuses must be listed in the order they appear in the device.
• The E field must be listed before the C (checksum) field. If the U field
is used, the E field must come before the U (user data) field.
• The E field is specified using binary numbers, since the full number
of E-field cells is otherwise unknown.
• The number of cells specified in the E field is not included in the QF
(number of fuses) field.
• The E-field cells are included in the C (fuse checksum) field.
• The E field reads left to right for the purpose of checksum calculation.
The syntax for the E field is as follows:
<Electrical Data Fuse List>::’E’<binary digit(s)>’*’
The character E begins the E field and is followed by one binary digit for
each E fuse. Each binary digit indicates one of two possible states (zero,
specifying a low-resistance link, or one, specifying a high-resistance link)
for each fuse. For example,
QF24*
L0000
101011000000000000000000*
E10100111*
C011A*
U10110110*