Hi,
I wrote some VHDL code for the Cyclone V FPGA with ALTLVDS_RX function. Can I use the same code for the MAX10 FPGA? Regards.Link Copied
Why don't you try it?
If not mistaken, the Max10 support LVDS using soft logic serdes. I think the same CV ALTLVDS_RX might not work if you compile directly. But you could give it a try also. If not working, then try re-instantiate the IPs.
--- Quote Start --- Why don't you try it? --- Quote End --- yeah.... just change the device selection and spend a little bit of time to see what is the compilation result.
You can also check in the ALTLVDS_RX user guide to see if there is any device family support list.
what usage you downgrade from cyclone V to MAX10??
Probably to save the cost of flash since Max devices support on chip memory for configuration.
I think the best would to be try out compilation with design in both device to see if can fit or not. Max 10 is of much lesser logic as compare to CV.
MAX10 is a huge downgrade in term of performance compared to cyclone V. your usage really that simple allow you for such down grade?
Agree with pororo. Generally switch from FPGA to CPLD might bump into logic resource concern.
Don't get confused by MAX 10 classification as "CPLD". It's a full featured FPGA with flash configuration memory and can well keep up with previous FPGA families like Cyclone III and has quite similar logic core features.
The other MAX devices are more like FPGAs than CPLDs.
By looking at the overview chapter of Max 10 and CV handbook, the smallest devices' LE is 2k (Max10) vs 25k (CIV) which seems to be significant.
i believe cost is not your constraint as you started in cyclone V at the first place, so just stick to cyclone V, better support in feature.
I think it would be back to the initial requirement of your design and applications. Need to evaluate if you can achieve the design in Max or need Cyclone. You can sit with your local FAE for part selection. Or you can also use the part selector tool in Altera web to assist in part selection.
For more complete information about compiler optimizations, see our Optimization Notice.