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.3.3. Example of Calculating DRAM Required by Jam STAPL Byte-Code Player

To determine memory usage, first determine the amount of ROM required and then estimate the RAM usage.

This example uses a 16-bit Motorola 68000 processor to program EPM7128AE and EPM7064AE devices in an IEEE Std. 1149.1 JTAG chain using a compressed .jbc.

  1. Use the multi-device equation to estimate the .jbc size.
    Figure 15. Multi-Device Equation to Estimate .jbc Size


    • Because the .jbc file contains compressed data, use the compressed data file size constants to determine the data size. Refer to the related information.
    • In this example, Alg is 21 KB and Data is the sum of EPM7064AE and EPM7128AE data sizes (8 KB + 4 KB = 12 KB).
    • The the .jbc file size is 33 KB.
  2. Estimate the Jam STAPL Byte-Code Player size—this example uses a Jam STAPL Byte-Code Player size of 62 KB because the Motorola 68000 processor is a 16 bit processor. Use the following equation to determine the amount of ROM required. In this example, the ROM size is 95 KB.
    Figure 16. Equation to Estimate the Maximum Required ROM Size


  3. Estimate the RAM usage using the following equation. In this example, the .jbc size is 33 KB.
    Figure 17. Equation to Estimate Maximum Required DRAM


    • Because the .jbc uses compressed data, add up the uncompressed data size for each device to find the total amount of RAM usage. Refer to the related information.
    • The uncompressed data size constants for EPM7064AE and EPM7128AE are 8 KB and 12 KB, respectively.
    • The total DRAM usage in this example is calculated as RAM Size = 33 KB + (8 KB + 12 KB) = 53 KB.
In general, .jam files use more RAM than ROM. This characteristic is desirable because RAM is cheaper. In addition, the overhead associated with easy upgrades becomes less of a factor when programming a large number of devices. In most applications, the importance of easy upgrades outweigh memory costs.
Related Information
Level Two Title