Forum Discussion

dim1's avatar
dim1
Icon for New Contributor rankNew Contributor
4 months ago
Solved

LPDDR4 not available in NIOSV/g linker script - Agilex-5, Quartus 26.1 Pro

Hello, I have a simple design for Agilex 5, using NIOS V/g and EMIF IP with LPDDR4 memory. I have the NIOS V instruction and data manager ports connected to the EMIF IP. Design compiles Ok. But...
general
Nios Architecture
  • LiangYuG_Altera's avatar
    LiangYuG_Altera
    2 months ago

    Hi dim1​ 

    Got it.

    (This may come rather late for you, sorry about that. But I believe you will be interested in this new findings.)

    There is another workaround for the Agilex 5 & 3 EMIF IP involving the isMemoryDevice agent information.

    You may refer to this KDB.

    Unlike the Add Memory Device workaround, this one is tied to QSYS. As such, isMemoryDevice workaround (repeat per new QSYS) is less repetitive compared Add Memory Device workaround (repeat per new BSP).

    Besides that, the isMemoryDevice workaround fixes the problem from the roots in Platform Designer. Thus, the subsequent BSP Editor will work seamlessly (the experience of EMIF IP in BSP Editor will be akin to a OCRAM IP). 

    Regards,
    Liang Yu

dim1's avatar
dim1
Icon for New Contributor rankNew Contributor
2 months ago

Never mind. It actually works, even though it shows two devices with the same name.

Thank you,

D.

  • LiangYuG_Altera's avatar
    LiangYuG_Altera
    Icon for Contributor rankContributor
    2 months ago

    Hi dim1​ 

    Got it.

    (This may come rather late for you, sorry about that. But I believe you will be interested in this new findings.)

    There is another workaround for the Agilex 5 & 3 EMIF IP involving the isMemoryDevice agent information.

    You may refer to this KDB.

    Unlike the Add Memory Device workaround, this one is tied to QSYS. As such, isMemoryDevice workaround (repeat per new QSYS) is less repetitive compared Add Memory Device workaround (repeat per new BSP).

    Besides that, the isMemoryDevice workaround fixes the problem from the roots in Platform Designer. Thus, the subsequent BSP Editor will work seamlessly (the experience of EMIF IP in BSP Editor will be akin to a OCRAM IP). 

    Regards,
    Liang Yu

    • dim1's avatar
      dim1
      Icon for New Contributor rankNew Contributor
      1 month ago

      Hello Liang Yu,

      The QSYS workaround is simpler, and resolved the issue.

      Thank you!

      D.