Honored Contributor
Honored ContributorHi KxAlpha..
You are the second person in the last week, that has brought this up on the forum, and the should should Altera how much of an issue this really is, but they still don't get it. Altera's solution is to select all possible family members in the same package as "Migration Devices" with your IO's selected then compile the design. Quartus will then produce a .pin file or error out if you have an issue, that will describe all pins. and "should" handle all the migration issues. What I want is a pin-out excel sheet that does the same thing but they do these by device, and you end up running into the issues you described. My solution is to take all the device excel pin-outs for a particular package and do a merge for that package, so I know what the least common denominator is. I then use that spreadsheet to create an orcad symbol for the "migration" device. Pete
