Cyclone IV and Cyclone V PowerPlay Early Power Estimator Download

The Cyclone® IV and Cyclone V PowerPlay Early Power Estimator results are based on measured power data. The Cyclone IV and Cyclone V PowerPlay Early Power Estimator provides a current (ICC) and power (P) estimate based on typical conditions (room temperature and nominal VCC). These calculations should only be used as an estimation of power, not as a specification. You should verify the actual ICC during device operation, as this measurement is sensitive to the actual pattern in the device and the environmental operating conditions.

Instructions for Using the PowerPlay Early Power Estimator for Cyclone IV and Cyclone V Devices

  1. To use the Cyclone IV and Cyclone V PowerPlay Early Power Estimator, Microsoft Excel software must be installed on your computer.
  2. Open the spreadsheet, select the targeted family and packages from the Input Parameter section in the Main tab of the PowerPlay Early Power Estimator.
  3. Enter the resources that you will be using in the design. Make sure that the toggle rate of the resources matches the hardware performance.
  4. Go back to the Main tab to check the total power, static power, power supply current, and so on.

The PowerPlay Early Power Estimator for Cyclone IV and Cyclone V devices support the Microsoft Excel version stated below:

Microsoft Excel 93-2007 &
Microsoft Excel 2010 (32 bit and 64 bit)

Download Estimator

Note: A macro is embedded within the PowerPlay Early Power Estimator for Cyclone IV and Cyclone V devices that allows you to reset all user-entered values. If you disable the macro, you must manually reset all user-entered values.

 

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 in the PowerPlay Early Power Estimator (EPE) tool. This is due to a Microsoft security update. 

Microsoft has released an update to fix this issue, please go to the corresponding Microsoft Support Page based on your Excel:

Excel 2007:
https://support.microsoft.com/en-us/kb/2956103

Excel 2010:
https://support.microsoft.com/en-us/kb/2956142

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:

1.      Reboot the computer if you've installed the above update

2.      Close all Microsoft Office applications including Excel and Word

3.      Open a Windows Explorer, and enter "%temp%" (without quotes) into the address bar

4.      Press "Ctrl" + "F" and enter ".exd" (without quotes) into the search box

5.      If any files with extension ".exd" are found, select and delete ALL found files

6.      Next, enter "%appdata%" (without quotes) into the address bar. Again, press "Ctrl" + "F" and search for ".exd", and delete ALL found files

7.      Reopen the EPE

If the issues remain, please follow these steps:

1.      Open the EPE tool, go to "File" -> "Info" -> "Compatibility Mode" and click the "Convert" button

2.      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 in the PowerPlay Early Power Estimator (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 infomraiton 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:    
https://support.microsoft.com/kb/2726958