5.10 Handoff Design for Production

The Configure Security Locks for Production is a GUI-based tool that guides PolarFire and PolarFire SoC users on how to configure security locks for production. The tool also allows PolarFire SoC users to configure one-way passcode for production.

The wizard has six steps that are executed in sequential order. One Time Programmable (OTP) settings are applied to configured Security settings from the Configure Security tool. The subsequent pages in the wizard have read-only fields that will be affected by settings for Permanent Locks (and One-way Passcode for PolarFire SoC). These settings can be configured only by the Configure Security tool.

If you configure any Permanent Lock settings in the wizard, you will be forced to go through each page to review the settings to make sure they are as desired. If PolarFire SoC users enable Enable One-way Passcode (OWP), the Finish button becomes active and users are not required to go through each page.

The settings cannot be changed once they have been programmed.

1. Permanent Locks
2. User Keys in Configure Security
3. Update Policy in Configure Security
4. Debug Policy in Configure Security
5. Microsemi Factory Access in Configure Security
6. JTAG/SPI Slave Commands Policy in Configure Security

The Export Bitstream tool allows you to export PPD, STAPL, DAT, and SPI programming files. It also allows SmartFusion 2 users to export SVF files.

PolarFire users can use Export Bitstream to export the Fabric with sNVM. PolarFire SoC users can use Export Bitstream to export either the Fabric with sNVM or the sNVM component only.

To export a bitstream file:

1. Under Handoff Design for Production, double click Export Bitstream. The Export Bitstream dialog box opens. The dialog box options depend on the device family, Custom Security settings, and Permanent Locks (and One-way Passcode for PolarFire SoC) for production settings:
   • Device Configured with Bitstream Encryption with Default Key in the Configure Security Tool (PolarFire and PolarFire SoC)
   • Device Configured with Custom Security Option in the Configure Security Tool (PolarFire and PolarFire SoC)
   • Device Configured with Security Locks for Production Tool (PolarFire)
   • Device Configured with Bitstream Encryption with Default Key in the Security Policy Manager (SmartFusion 2 and IGLOO 2)
   • Device Configured with Custom Security Option in the Security Policy Manager (SmartFusion 2 and IGLOO 2)
   • Export Bitstream (RTG4)
2. Enter your bitstream file name and select the location to export the bitstream file.
3. Choose the options that apply to your device (see Export Bitstream Dialog Box Options).
4. Click OK to export the selected bitstream files.

The following topics describe the exporting of FlashPro Express jobs.

Job Manager is Microchip's HSM-based security software for job management. It is supported by PolarFire SoC, PolarFire, SmartFusion 2, and IGLOO 2.

To export Job Manager data:

1. In the Design Flow window, expand Handoff Design for Production.
2. Double-click Export Job Manager Data.
3. Complete the fields in the Export Job Manager Data dialog box.
4. Click OK.

Table 5-121 5-122 5-123. Fields in the Export Job Manager Data Dialog Box

Field	Description
Name	All names use a prefix as shown in your software.
Location	Location of the file to be exported.
Existing programming data files	Existing programming job files already in your project.
Include bitstream components	Components of the design that can be saved to the file.
Include SPI Flash data (requires Fabric/sNVM components)	PolarFire only: If SPI Flash is configured in Configure Design Initialization Data and Memories, use this option to include Fabric/sNVM components.
Bypass Black Level protection for Recovery/Golden bitstream	Bypasses black-level protection for the SPI bitstream.

The Export SPI Flash Image tool allows PolarFire and PolarFire SoC users to export a SPI Flash Image file. The SPI Flash is defined in the SPI Flash tab in the Configure Design Initialization Data and Memories tool.

To export the SPI Flash Image:

1. In the Design Flow window, expand Handoff Design for Production.
2. Double-click Export SPI Flash Image.
3. Complete the fields in the Export SPI Flash Image dialog box.
4. Click OK.

Table 5-121 5-122 5-123. Fields in the Export SPI Flash Image Dialog Box

Field	Description
Name	All names use a prefix as shown in your software.
Location	Location of the file to be exported.
Existing files	Existing files already in your project.

The pin report lists the pins in your device. When you export the report, you can specify whether you want the pins to be sorted by port name, package pin name, or both. Based on your selection, the pin report generates one or two files:

• <design>_pinrpt_name.rpt. Pin report sorted by name.
• <design>_pinrpt_number.rpt. Pin report sorted by pin number.

By default, exporting a pin report generates a Bank report with the filename <design>-bankrpt.rpt. Export Pin Report also generates an I/O Register Combining report that lists the I/Os that are combined into a Register to improve timing performance.

The BSDL file provides a standard file format for electronics testing using JTAG. It describes the boundary scan device package, pin description, and boundary scan cell of the input and output pins. BSDL models are available as downloads for many Microchip SoC devices.

To generate the BSDL file to your Design Report:

For more information about BSDL models, see the Microchip website.

Export Input Output Buffer Information Specification (IBIS) is supported for all PolarFire “T” devices, except the “XT” device. The Export IBIS feature is supported in two stages:

• Pre-Layout Flow
• Post-Layout Flow

To export the IBIS Model in the Pre-Layout Flow, the design must pass until the Synthesis/Compile stage. You must provide the I/O placement and configuration details in the I/O PDC files to export the resultant IBIS files in Pre-Layout Flow.

To export the IBIS Model in the Post-Layout Flow, the design must pass until the Place and Route stage. If a design runs through the Place and Route tool, the IBIS model for the Post-Layout Flow will be exported by default.

To export the IBIS Model:

1. In the Design Flow window, expand Handoff Design for Production.
2. Double-click Export IBS Model.
3. Complete the fields in the Export IBS Model dialog box.
4. Click OK.

RTG4 users can generate an Export μPROM report that includes the configuration file path, client details, and μPROM usage statistics.

To export a μPROM report:

1. In the Design Flow window, expand Handoff Design for Production.
2. Double-click Export μPROM Report to export the report. The Export μPROM Report Under dialog box appears.
3. When prompted, go to the location where you want to save the Export μPROM report.
4. Click Select Folder.

The Export uPROM report generates an XML/TEXT version of the report with the filename. For example: uPROM_Configuration_Report.xml/ uPROM_Configuration_Report.txt