9–12
Chapter 9: Using User Flash Memory in MAX II Devices
Programming and Reading the UFM with JTAG
Figure 9–10.
UFM Erase Waveforms
ARShft
ARClk
ARDin
DRShft
DRClk
DRDin
DRDout
OSC_ENA
Program
Erase
Busy
t
EB
t
EPMX
t
BE
t
OSCS
t
OSCH
t
ADS
t
ASU
t
ACLK
9 Address Bits
t
AH
t
ADH
Programming and Reading the UFM with JTAG
In Altera MAX II devices, you can write or read data to/from the UFM using the IEEE
Std. 1149.1 JTAG interface. You can use a PC or UNIX workstation, the Quartus II
Programmer, and the ByteBlaster
TM
MV or ByteBlaster
TM
II parallel port download
cable to download Programmer Object File (.pof), Jam
TM
Standard Test and
Programming Language (STAPL) Files (.jam), or Jam Byte-Code Files (.jbc) from the
Quartus II software targeting the MAX II device UFM block.
1
The POF, Jam File, or JBC File can be generated using the Quartus II software.
Jam Files
Both Jam STAPL and JBC files support programming for the UFM block.
Jam Players
Jam Players read the descriptive information in Jam files and translate them into data
that programs the target device. Jam Players do not program a particular device
architecture or vendor; they only read and understand the syntax defined by the Jam
file specification. In-field changes are confined to the Jam file, not the Jam Player. As a
result, you do not need to modify the Jam Player source code for each in-field
upgrade.
There are two types of Jam Players to accommodate the two types of Jam files: an
ASCII Jam STAPL Player and a Jam STAPL Byte-Code Player. Both ASCII Jam STAPL
Player and Jam STAPL Byte-Code Player are coded in the C programming language
for 16-bit and 32-bit processors.
f
For guidelines on UFM operation during ISP, refer to the
chapter in the
MAX II Device Handbook.