Visible to Intel only — GUID: oey1554481033284
Ixiasoft
1.1. Supported Devices and Configuration Methods
1.2. Quad SPI Flash Byte-Addressing
1.3. Generic Flash Programmer Operation
1.4. Generic Flash Programmer Flow Templates (Convert Programming File)
1.5. Generic Flash Programmer Settings Reference
1.6. Generic Flash Programmer User Guide Revision History
1.4.1. Initialization Flow Templates (Convert Programming File)
1.4.2. Program Flow Template (Convert Programming File)
1.4.3. Erase Flow Template (Convert Programming File)
1.4.4. Verify/Blank-Check/Examine Flow Template (Convert Programming File)
1.4.5. Termination Flow Template (Convert Programming File)
1.4.6. Programming Flow Action Properties
Visible to Intel only — GUID: oey1554481033284
Ixiasoft
1.3.1.2.2. Defining a New Flash Memory Configuration Device
You can define and store the settings for a new flash memory device, based on the programming flow template of an existing supported flash memory device. You can customize and preserve the properties of the new flash memory device as a template for subsequent reuse, and define other flash memory devices based the template.
When you define a new flash memory device, Intel® Quartus® Prime software stores the collection of settings in an .xml file automatically in the Custom database directory location that you can specify.
Define New Flash Device ( Intel® Arria® 10 Example)
Follow these steps to define a new flash memory device:
- Generate a .jic file for flash programming, as Step 2: Generate Secondary Programming Files (Convert Programming Files) describes.
- For the Configuration Device option, select <<new device>>. The settings on this and other tabs become available.
- For Programming flow template, select an existing flash memory device template for the new device initial settings, or define a flash programming flow for a different flash memory vendor based on an existing template.
- Specify the remaining settings on the Configuration Device tab:
Table 3. Configuration Device Tab Settings Option Description Device name Specify a unique name for the flash not already listed in the Name column. The Name must not contain any empty string (space) or special characters (except "_"). Device ID Specify the 3-byte ID that the Programmer Auto-Detect operation uses to detect the flash programming device, such as 0x20 0xBB 0x21. Device I/O voltage Specify 1.8V or 3.0/3.3V to match your memory device specification. Device density Select the total density that corresponds with your flash memory device size. Total device die Specify the total number of die for a stacked device (where applicable). Single I/O mode dummy clock Specify the Fast Read dummy clock cycle for flash device in single I/O protocol. The programming file generation uses this setting to determine if the configuration requires bit shifting to compensate for the actual dummy clock cycle during Active Serial configuration. Quad I/O mode dummy clock Specify the Fast Read dummy clock cycle for flash device in Quad I/O protocol. The programming file generation uses this setting to determine if the configuration requires bit shifting to compensate for the actual dummy clock cycle during Active Serial configuration. Custom database directory Specifies the location of the .xml file that preserves a flash memory device definition and flow information. The default location is the project directory or current working directory. Note: When you specify a non-default folder for the Custom database directory location, place the .sof and .jic files in the same folder as the .xml file to avoid missing a defined flash database or corruption of the .jic file.Save as template Enable this option and specify a unique name to save the current flash memory device definition as a template for later use. Programming File Generator saves the template in the Custom database directory. Click the Edit button to delete any templates you save. - For supported FPGA devices, optionally modify any of the default programming flows for the flash memory device, as Modifying Programming Flows describes.
Note: When you modify a programming flow, all .jic files using this programming flow are affected. For example, you can define a new micron_1gb flow, and then use this device to define the micro_1gb_partA.jic file. Later, you modify themicron_1gb flow, and then use this flow to create micro_1gb_partB.jic. In this example, micro_1gb_partA programming flow reflects the latest modifications to micron_1gb.