AN 425: Using the Command-Line Jam STAPL Solution for Device Programming

Download PDF
ID 683089
Date 12/09/2016
Public
Document Table of Contents
Document Table of Contents x
1. Using the Command-Line Jam STAPL Solution for Device Programming
1. Using the Command-Line Jam STAPL Solution for Device Programming x
1.1. Jam STAPL Players 1.2. Jam STAPL Files 1.3. Using the Jam STAPL Player 1.4. Using the quartus_jli Command-Line Executable 1.5. Using Jam STAPL for ISP with an Embedded Processor 1.6. Board Layout 1.7. Embedded Jam STAPL Players 1.8. Updating Devices Using Jam 1.9. Document Revision History
1.1. Jam STAPL Players x
1.1.1. Differences Between the Jam STAPL Players and quartus_jli
1.2. Jam STAPL Files x
1.2.1. Generating Byte-Code Jam STAPL Files 1.2.2. List of Supported .jam and .jbc Actions and Procedures 1.2.3. Jam STAPL Player and quartus_jli Exit Codes
1.2.2. List of Supported .jam and .jbc Actions and Procedures x
1.2.2.1. Definitions of .jam and .jbc Action and Procedure Statements
1.4. Using the quartus_jli Command-Line Executable x
1.4.1. Command-line Syntax of quartus_jli Command-Line Executable
1.5. Using Jam STAPL for ISP with an Embedded Processor x
1.5.1. Methods to Connect the JTAG Chain to the Embedded Processor
1.5.1. Methods to Connect the JTAG Chain to the Embedded Processor x
1.5.1.1. Connecting the Embedded Processor Directly to the JTAG Chain 1.5.1.2. Connecting the JTAG Chain to an Existing Bus Using an Interface Device
1.6. Board Layout x
1.6.1. Treat the TCK Signal Trace as a Clock Tree 1.6.2. Use a Pull-Down Resistor on the TCK Signal 1.6.3. Make the JTAG Signal Traces as Short as Possible 1.6.4. Add External Resistors to Pull the Outputs to a Defined Logic Level
1.7. Embedded Jam STAPL Players x
1.7.1. The Jam STAPL Byte-Code Player 1.7.2. Steps to Port the Jam STAPL Byte-Code Player 1.7.3. Jam STAPL Byte-Code Player Memory Usage
1.7.2. Steps to Port the Jam STAPL Byte-Code Player x
1.7.2.1. Step 1: Set the Preprocessor Statements to Exclude Extraneous Code 1.7.2.2. Step 2: Map the JTAG Signals to the Hardware Pins 1.7.2.3. Step 3: Handle Text Messages from jbi_export() 1.7.2.4. Step 4: Customize Delay Calibration
1.7.3. Jam STAPL Byte-Code Player Memory Usage x
1.7.3.1. Estimating ROM Usage 1.7.3.2. Estimating Dynamic Memory Usage 1.7.3.3. Example of Calculating DRAM Required by Jam STAPL Byte-Code Player
1.7.3.1. Estimating ROM Usage x
1.7.3.1.1. Algorithm File Size Constants 1.7.3.1.2. Compressed and Uncompressed Data Size Constants 1.7.3.1.3. Jam STAP Byte-Code Player Size
1.8. Updating Devices Using Jam x
1.8.1. jbi_execute Parameters 1.8.2. Running the Jam STAPL Byte-Code Player
1. Using the Command-Line Jam STAPL Solution for Device Programming

1.7.1. The Jam STAPL Byte-Code Player

The Jam STAPL Byte-Code Player is coded in the C programming language for 16 bit and 32 bit processors. A specific subset of the player source code also supports some 8 bit processors.

The source code for the 16 bit and 32 bit Jam STAPL Byte-Code Player is divided into two categories:

  • jbistub.c—platform-specific code that handles I/O functions and applies to specific hardware.
  • All other C files—generic code that performs the internal functions of the player.
Figure 10. Jam STAPL Byte-Code Player Source Code StructureThis shows the organization of the source code files by function. The process of porting the Jam STAPL Byte-Code Player to a particular processor is simplified because the platform-specific code is all kept inside jbistub.c.


Related Information
Level Two Title