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

Download PDF
ID 683089
Date 10/14/2024
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 for AN 425: Using the Command-Line Jam™ STAPL Solution for Device Programming
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™ STAPL 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.1.2. Compressed and Uncompressed Data Size Constants

Table 10.  Data Constants for Altera® Devices Supporting the Jam Language (for ISP)In this table, the enhanced configuration devices (EPC) data sizes use a compressed Programmer Object File (.pof).
Device Typical Jam STAPL Byte-Code Data Size (KB)
Compressed Uncompressed4
EP1S10 105 448
EP1S20 188 745
EP1S25 241 992
EP1S30 320 1310
EP1S40 369 1561
EP1S60 520 2207
EP1S80 716 2996
EP1C3 32 82
EP1C6 57 150
EP1C12 100 294
EP1C20 162 449
EPC4 5 242 370
EPC85 242 370
EPC86 547 822
EPC165 242 370
EPC167 827 1344
EP1SGX25 243 992
EP1SGX40 397 1561
EP1M120 30 167
EP1M350 76 553
EP20K30E 14 48
EP20K60E 22 85
EP20K100E 32 130
EP20K160E 56 194
EP20K200E 53 250
EP20K300E 78 347
EP20K400E 111 493
EP20K600E 170 713
EP20K1000E 254 1124
EP20K1500E 321 1509
EP2A15 107 549
EP2A25 163 788
EP2A40 257 1209
EP2A70 444 2181
EPM7032S 8 8
EPM7032AE 6 6
EPM7064S 13 13
EPM7064AE 8 8
EPM7128S, EPM7128A 5 24
EPM7128AE 4 12
EPM7128B 4 12
EPM7160S 10 28
EPM7192S 11 35
EPM7256S, EPM7256A 15 51
EPM7256AE 11 18
EPM7512AE 18 37
EPM9320, EPM9320A 21 57
EPM9400 21 71
EPM9480 22 85
EPM9560, EPM9560A 23 98
EPF10K10, EPF10K10A 12 15
EPF10K20 21 29
EPF10K30 33 47
EPF10K30A 36 51
EPF10K30E 36 59
EPF10K40 37 62
EPF10K50, EPF10K50V 50 78
EPF10K50E 52 98
EPF10K70 76 112
EPF10K100, EPF10K100A, EPF10K100B 95 149
EPF10K100E 102 167
EPF10K130E 140 230
EPF10K130V 136 199
EPF10K200E 205 345
EPF10K250A 235 413
EP20K100 128 244
EP20K200 249 475
EP20K400 619 1,180
EPC2 136 212
EPM240 12.48 12.4
EPM570 11.4 19.6
EPM1270 16.9 31.9
EPM2210 24.7 49.3
MAX V 9 9
MAX 10 9 9
4 For more information about how to generate .jbc with uncompressed programming data, refer to Altera FPGA Support.
5 The programming file targets one EP1S10 device.
6 The programming file targets one EP1S25 device.
7 The programming file targets one EP1S40 device.
8 There is a minimum limit of 64 kilobits (Kb) for compressed arrays with the .jbc compiler. Programming data arrays that are smaller than 64 Kb (8 kilobytes (KB)) are not compressed. The EPM240 programming data array is below the limit, which means that the .jbc files are always uncompressed. A memory buffer is needed for decompression. For small embedded systems, it is more efficient to use small uncompressed arrays directly rather than to uncompress the arrays.
9 The file size is design dependent. Refer to the generated .jbc file for the file size.
Level Two Title