Migration from EP3C80F780 to EP3C120F780

Migration is one pet peeve of miine with Altera. They need to provide a "Migration" pinout file:

If you look at the "Maximum User IO's in table 3 of the overview page you can see the potential issues:

http://www.altera.com/devices/fpga/cyclone3/overview/cy3-overview.html

The 780 package has migration capability between the C40, C55, C80 and C120. However, the maximum number of io's change between the family members.

The C40 has 545, C55 has 377 the C80 has 429 and the C120 has 531. So to be truely migratable, you need to limit the design to no more than 377 IO's.

If you look closely at the pinout's you find that on some of the devices certain pins are NC, others are VCCIO's others are GND. depending on the family member.

So you apparently have made it passed the first step, in the design compiled with the existing pinout targeting the larger device. However, you need to also very that the Layout is "Truely" compatible for the larger device, in that all VCCIO's and GND's are connected as such (they may have been IO's on the C80).

To truly validate this, I take the spreadsheet for all family members in a particular package, and cross reference the pinouts, to vaildate all configuration pins, and all VREF's, clocks, VCC's GND's etc for every pin. Making a "Migration" pinout spreadsheet, that I then use to guild the layout

I have requested ALTERA produce this time and time again, but so far no one is listening. They say the "Migration" option in the tool will tell you. But it won't tell you that the IO's you aren't using in this device are VCCIO or GND in the next device up.

And most of the time, you are defining the pinout before you have a design done, because you need the board, so it's nice to know the pins your are selecting are "ALWAYS" good, and not happened to be good because the logic behind them got optimized out, because it isn't there yet.

Grumble...

On your other question. If the pinout is good and the board power is good to support the larger device, your timing is probably different.

Make sure your timing reports are clean. It could be that's your problem.

Pete