Ok, this table is coming through right, but I'm seeing an issue with Max 10 PowerUsing the same design, I see the IO power is about 600 mW too high on MAX 10. I was just wondering if anyone else is seeing a similar issue. Here are the numbers 25K LE 30K LE 30K LE 49K LE 25K LE 50K LE EP3C25F324I7 EP4CE30F19A7 EP4CE30F19A7 5CEBA4F17i7 10M25DAF256I7G 10M50DAF256I7G Total Thermal (mW) 353.25 350.3 371.29 391.97 1029.38 1097.51 Core Dynamic (mW) 243.79 224.11 224.11 139.84 255.18 264.35 Core Static (mW) 90.09 91.92 112.72 243.13 152.98 204.95 IO Thermal (mW) 19.37 34.27 34.27 9 621.22 628.21 Core Toggle Rate 25.00% 25.00% 25.00% 25.00% 25.00% 25.00% IO Toggle Rate 12.00% 12.00% 12.00% 12.00% 12.00% 12.00% Release 13.1.3 Build 178 15.0.0 Build 145 15.0.0 Build 145 15.0.0 Build 145 15.0.0 Build 145 15.0.0 Build 145 25 C 25C 70C 70C 70C 70C Heatsink/airflow Heatsink/airflow no heat sink/airflow no heat sink/airflow no heat sink/airflow no heat sink/airflow Thanks Pete
By looking at the Max 10 vs Cyclone V, it seems like Max 10 IO is ~20x of the Cyclone V IO in term of power consumption. Personally I think this is bit high comparatively. I think you should contact Altera to seek further clarification if this is something expected with Max 10 IO power consumption.
I have placed a service issue with Altera on this. I have received much more reasonable results exporting the cvs and using the spreadsheet based Early Power Estimator for the Max 10.I provided both to Altera, and we'll see if they come out with a hotfix for Quartus for this issue. Pete
Hi Pete,Thanks for reporting this to Altera and sharing that this is a bug with Quartus II 15.0. I believe the current workaround would be to use the Early Power Estimator until the fix.