AN 904: Intel® MAX® 10 Hitless Update Implementation Guidelines

Download PDF
ID 683380
Date 5/26/2023
Public
Document Table of Contents
Document Table of Contents x
1. Intel® MAX® 10 Hitless Update Implementation Guidelines
1. Intel® MAX® 10 Hitless Update Implementation Guidelines x
1.1. Introduction 1.2. Types of Intel® MAX® 10 Design Update Flow 1.3. Stages of Intel® MAX® 10 Hitless Update Flow 1.4. Intel® MAX® 10 Hitless Update Requirement and Limitation 1.5. Hitless Update using Intel® Quartus® Prime Programmer 1.6. Hitless Update using Intel® Jam STAPL Byte-Code Player 1.7. Hitless Update Using Self-Developed Algorithm 1.8. Boundary-Scan Pattern Configuration Bit Location 1.9. JTAG Instructions 1.10. Sample of Hitless Update Algorithm in Jam Format 1.11. Document Revision History for AN 904: Intel® MAX® 10 Hitless Update Implementation Guidelines
1.5. Hitless Update using Intel® Quartus® Prime Programmer x
1.5.1. Creating IPS File 1.5.2. Executing IPS File
1.6. Hitless Update using Intel® Jam STAPL Byte-Code Player x
1.6.1. Generating .jam/.jbc File 1.6.2. Interpreting Jam File Information using Jam Player
1.7. Hitless Update Using Self-Developed Algorithm x
1.7.1. Custom Algorithm Implementation Flow for Intel® MAX® 10 Devices with SC/SA/SL/DC/DF/DA Feature Options 1.7.2. Custom Algorithm Implementation Flow for Intel® MAX® 10 Devices with DD Feature Option
1. Intel® MAX® 10 Hitless Update Implementation Guidelines

1.6.2. Interpreting Jam File Information using Jam Player

The Jam Player is a C program that parses the Jam file, interprets each Jam STAPL instruction, and reads and writes data to and from the JTAG chain.

The variables processed by the Jam Player depend on the initialization list variables present at the time of execution. Because each application has unique requirements, you can easily modify the Jam Player source code.

For more information about JAM Player, contact Intel Premier Support and quote ID #15012870482.

Figure 4. Jam Player Source Code Structure
Note: The JTAG I/O pins are TCK, TMS, TDI, and TDO.

The main program performs all of the basic functions of the Jam Player without modification. You must only modify the I/O functions. They are contained in the jamstub.c file, as shown in the figure above, and include functions which specify addresses to I/O pins, delay routines, operating system-specific functions, and routines for file I/O pins. You can customize these functions by simply editing the jamstub.c file then compile the source code for use on any platform.

The Jam Player resides permanently in system memory, where it interprets the commands given in the Jam file and generates a binary data stream for device programming. This structure confines all upgrades to the Jam file, and allows the Jam Player to adapt to any system architecture.

Related Information
Level Two Title