AN 425: Using the Command-Line Jam™ STAPL Solution for Device Programming
In Collections:
Intel® MAX® 10 FPGAs SupportCyclone® III FPGA SupportCyclone® V FPGAs and SoC FPGAs SupportStratix® IV FPGAs SupportStratix® III FPGA SupportMAX® II CPLDs SupportCyclone® IV FPGAs SupportArria® II FPGA SupportIntel® Arria® 10 FPGAs SupportFPGA Documentation IndexMAX® V CPLDs SupportArria® V FPGAs and SoC FPGAs SupportIntel® Stratix® 10 FPGAs and SoC FPGAs Support
ID
683089
Date
10/14/2024
Public
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.7.3.1. Estimating ROM Usage
Figure 12. Equation to Estimate the Maximum Required ROM SizeUse this equation to estimate the maximum amount of ROM required to store the Jam™ STAPL Byte-Code Player and the .jbc.
The .jbc size can be separated into these categories:
- The amount of memory required to store the programming data.
- The space required for the programming algorithm.
Figure 13. Equation to Estimate .jbc Size
This equation provides a .jbc size estimate that may vary by ±10%, depending on device utilization. If device utilization is low, .jbc sizes tend to be smaller because the compression algorithm used to minimize file size will more likely find repetitive data.
This equation also indicates that the algorithm size stays constant for a device family but the programming data size grows slightly as more devices are targeted. For a given device family, the increase in the .jbc size caused by the data component is linear.