Early Power Estimator Download Intel® Cyclone® 10 GX Devices
The early power estimator results for Intel Cyclone 10 GX devices are based on preliminary and characterized power data. Any results obtained while using this estimator are preliminary. The Intel Cyclone 10 GX EPE (the "Program") provides a current (ICC) and power (P) estimate based on various typical conditions (such as room temperature and nominal VCC).
Note: The Program calculations are estimates only, and shall not be construed as a specification or a guarantee of any kind. The actual ICC should be verified during device operation, as this measurement is sensitive to the actual pattern in the device and the environmental operating conditions.
Instructions for Using the EPE for Intel Cyclone 10 GX Devices
- To use the EPE for Intel Cyclone 10 GX devices, Microsoft Excel must be installed on your computer.
- Open the spreadsheet and enable macros if prompted. By default, the macro security level in Microsoft Excel 2003, Microsoft Excel 2007, and Microsoft Excel 2010 is set to High. If the macro security level is set to High, macros are automatically disabled. For the features in the EPE spreadsheet to function properly, you must enable macros. For details on how to enable macros for your version of Microsoft Excel, please refer to the Setting Up the EPE for Intel Cyclone 10 GX section of the Early Power Estimator for Intel Cyclone 10 GX User Guide.
- Select the target device and package from the Input Parameters section in the Main worksheet of the EPE.
- Enter the resources used in the design. Make sure the toggle rates and other parameters match actual values that will be used in the design.
- After entering all the resources in the Early Power Estimator, go to the Report worksheet to observe estimated total power, static power, power supply currents, etc.
The EPE for Intel Cyclone 10 GX devices support the Microsoft Excel version stated below:
Microsoft Excel 93-2007 & |
---|
Known Issue 1: You may observe the buttons do not work, or a run-time error “Object doesn’t support this property or method” appears when you open the EPE tool. This is due to a Microsoft security update.
Microsoft has released an update to fix this issue, please go to the following Microsoft Support page:
Excel 2013: https://support.microsoft.com/en-us/kb/2920754
If the above update doesn't fix the issue, or if you do not have access to these updates, following are the workarounds that you should try:
- Reboot the computer if you've installed the above update.
- Close all Microsoft Office applications including Excel and Word.
- Open a Windows Explorer, and enter "%temp%" (without quotes) into the address bar.
- Press "Ctrl" + "F" and enter ".exd" (without quotes) into the search box.
- If any files with extension ".exd" are found, select and delete ALL found files.
- Next, enter "%appdata%" (without quotes) into the address bar. Again, press "Ctrl" + "F" and search for ".exd", and delete ALL found files.
- Reopen the EPE.
If the issues remain, please follow these steps:
- Open the EPE tool, go to "File" -> "Info" -> "Compatibility Mode" and click the "Convert" button.
- If a pop-up appears, click "OK" to proceed with conversion, and then click "Yes" to reopen the workbook.
The previous steps convert the original ".xls" EPE file into a ".xlsm" file. The newly created file should not exhibit the original issue.
Microsoft's description for this issue can be found at:
https://support.microsoft.com/kb/2726958
Known Issue 2: You may observe Excel crashes, and an error message “Excel has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available” appears when you open the EPE tool. This is due to Excel 2013 stability issue.
To solve the problem, please install the Microsoft Office 2013 Service Pack 1. You can find more information about this update at Microsoft Support:
https://support.microsoft.com/en-us/kb/2817430
The previous steps convert the original ".xls" EPE file into a ".xlsm" file. The newly created file should not exhibit the original issue.
Microsoft's description for this issue can be found at: