Visible to Intel only — GUID: nty1707400116487
Ixiasoft
Visible to Intel only — GUID: nty1707400116487
Ixiasoft
2.4. Migration within a Package
Vertical migration starts with printed circuit board (PCB) land pattern compatibility. This allows for different-density devices within a package type to be supported by the hardware with certain considerations. The I/O resources may vary by the device density. Utilize the I/O that is common to "all" targeted densities first for maximum device flexibility.
In general, there are usually a pair of devices that are similar and mainly differ in logic density with direct compatibility. Additional device densities may be offered in that same package footprint (PCB land pattern) but may have different core resources, supported functions or other differences.
There may be other mechanical considerations to be aware of and to review. The Top Lid heat sink mounting area of the package may vary as can the overall height (Z), for example, R25A. Ensure compatibility with the thermal design of the system and its manufacturing flow.
Functional capability differences may also exist. This may include I/O, EMIF, temperature sensors, bit stream size, supported device features, power requirements, and the required decoupling capacitors.
In general, you must determine the largest density for the application and base the board design on those requirements. It is easier to scale down the power supply system than up for example.
Before fabricating the printed circuit board, you must run compilation checks in the Quartus® Prime Pro Edition design software to validate both pin and IP functional compatibility. Ensure that the compilation passes without any fitter error.
Refer to the Pin Migration Window to verify if pin assignments are compatible to different density devices in the same device package in the Quartus® Prime Pro Edition design software.
There are a number of special cases that are conditional migration examples and additional guidance from Intel is recommended to accommodate these cases. The following table lists the conditional migration examples and are flagged in the other tables with a footnote.
Conditional Migration | Differences | Package(s) | |
---|---|---|---|
AGF 019/023 R25A | AGF 022/027 R25A | Features, I/O Placement, Package Height | R25A |
AGI 022/027 R29A | AGI 041 R29D | Features, I/O Placement | R29A / R29D |
AGI 027 R31B | AGI 041 R31B | Features, I/O Placement | R31B |
AGI 022/027 R31B | AGM 032/039 R31B | Features (I-Series to M-Series) | R31B |
AGF 019/023 R31C | AGI 019/023 R31B | FHT XCVR (F-Series to I-Series) | R31C / R31B |
AGF 022/027 R31C | AGI 022/027 R31B | FHT XCVR (F-Series to I-Series) | R31C / R31B |
The tables in Series Package Options vs Tiles – Support I/O Counts section indicate the vertical migration supported by the common package land patterns.
For additional migration information, refer to the package information section in the respective Agilex™ 7 product tables.
You can also refer to the Device Migration section in the AN 886: Agilex™ 7 Device Design Guidelines for a discussion on the vertical, horizontal, and conditional migration between devices.