Machxo2 Jedec File Format - Lattice Semiconductor MachXO2 Programming And Configuration Usage Manual

Hide thumbs Also See for MachXO2:
Table of Contents

Advertisement

MachXO2 JEDEC File Format

All Lattice non-volatile devices support JEDEC files. Utilities are available in the Deployment Tool software for con-
verting the JEDEC file into other programming file formats, such as STAPL, SVF, or bitstream (hex or binary). The
relevant detail about the JEDEC file is provided in the table below for completeness.
Table 21. MachXO2 JEDEC File Format
JEDEC Field
Don't Care
Start-of-text
Header
Field Terminator
Note (Comment)
Fuse Count
Default Fuse State
Security Setting
OTP and Security Setting
MachXO2 Programming and Configuration Usage Guide
Syntax
Characters appearing before the ^B character are don't care. All character
My design
sets or internal language can be used here except ^B.
^B (Control-B 0x02) marks the beginning of the JEDEC file. Only ASCII
characters are legal after ^B. The character * is the delimiter to mark the
^B
ending of a JEDEC field. The CR and LF are treated as regular white
spaces and have no delimiter function in a JEDEC file.
The first field is the header, which does not have an identifier to indicate its
My design
start. Only ASCII characters are legal after ^B. The header is terminated by
an asterisk character *.
*
Each field in the JEDEC file will be terminated with an asterisk.
The key word N marks the beginning of the comment. It can appear any-
NOTE my design
where in the JEDEC file. Lattice's JEDEC files add "OTE" to the N key word
to make it a more meaningful word NOTE.
QF3627736
The key word QF identifies the total real fuse count of the device
The key word F identifies the fuse state of those fuses not included in the
link field. F0 = fill them with zeros (0), F1 = fill them with ones (1). It is
F0 or F1
defined for the purpose of reducing JEDEC file size. It has no meaning in
Lattice's JEDEC file. Lattice recommends using compression to reduce file
size instead.
G0 or G1
JEDEC standard defines G<0,1> to program security <0=no, 1=yes>
Lattice enhances the G field to cover OTP fuse programming as well.
G0, G1, G2, or G3
G<0=both no, 1=only security yes, 2=only OTP yes, 3=both yes>.
Description
40
1
.

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents