Forum Discussion

alexislms's avatar
alexislms
Icon for Contributor rankContributor
4 years ago
Solved

22.1 pro: set_instance_assignment not accepting wildcard?

Instead of doing: set_instance_assignment -name IO_STANDARD "HSSI DIFFERENTIAL I/O" -to sfp0 set_instance_assignment -name IO_STANDARD "HSSI DIFFERENTIAL I/O" -to sfp1 set_instance_assignment -na...
  • sstrell's avatar
    sstrell
    4 years ago

    Actually, you don't have to do a full compilation, just Analysis & Elaboration.

    But as mentioned, when you edit the .qsf manually and the design has not been compiled yet, when you use the wildcard, Quartus does not know about that object yet.

    If you were to use the GUI instead, you always have to perform at least Analysis & Elaboration first so signals and objects appear in the Pin Planner or the Assignment Editor. It's the same situation here.

ShengN_altera's avatar
ShengN_altera
Icon for Super Contributor rankSuper Contributor
4 years ago

Hi,


Then you have to open the project again and do compilation so Quartus can read the settings changes in .qsf file.


Best Regards,

Sheng

p/s: If any answer from community or Intel support are helpful, please feel free to mark as solution and give Kudos.


  • alexislms's avatar
    alexislms
    Icon for Contributor rankContributor
    4 years ago

    This has nothing to do with any compilation, it's a project setup step.
    Also the .qsf is loaded when the project is opened, not at the compilation. (this is a .qsf not .sdc)

    I can clearly see it by doing 1. and 2. after 4., the pin planner is still able to set the property without any compilation step.

    Please raise a ticket to have this bug fixed.

    Regards,