Chapter 14: Using Jam STAPL for ISP via an Embedded Processor
14–5
Software Development
For more information about porting the Jam Byte-Code Player, see “Porting the Jam
STAPL Byte-Code Player” on page 14–8.
Jam Files (.jam and .jbc)
Altera supports the following types of Jam files:
■
ASCII text files (.jam)
■
Jam Byte-Code files (.jbc)
ASCII Text Files (.jam)
Altera supports two types of Jam files:
■
JEDEC Jam STAPL format
■
Jam version 1.1 (pre-JEDEC format)
The JEDEC Jam STAPL format uses the syntax specified by the JEDEC Standard JESD-
71A specification. Altera recommends using JEDEC Jam STAPL files for all new
projects. In most cases, Jam files are used in tester environments.
Jam Byte-Code Files (.jbc)
JBC files are binary files that are compiled versions of Jam files. JBC files are compiled
to a virtual processor architecture, where the ASCII Jam commands are mapped to
byte-code instructions compatible with the virtual processor. There are two types of
JBC files:
■
Jam STAPL Byte-Code (compiled version of JEDEC Jam STAPL file)
Jam Byte-Code (compiled version of Jam version 1.1 file)
■
Altera recommends using Jam STAPL Byte-Code files in embedded applications
because they use minimal memory.
Generating Jam Files
The Quartus II software can generate both Jam and JBC file types. In addition, Jam
files can be compiled into JBC files via a stand-alone Jam Byte-Code compiler. The
compiler produces a functionally equivalent JBC file.
Generating JBC files directly from the Quartus II software is simple. The software tool
supports the programming and configuration of multiple devices from single or
multiple JBC files. Figure 14–3 and Figure 14–4 show the dialog boxes that specify the
device chain and JBC file generation in the Quartus II software.
© October 2008 Altera Corporation
MAX II Device Handbook