Forum Discussion

alexislms's avatar
alexislms
Icon for Contributor rankContributor
3 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
    3 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.

sstrell's avatar
sstrell
Icon for Super Contributor rankSuper Contributor
3 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.

alexislms's avatar
alexislms
Icon for Contributor rankContributor
3 years ago

That's now clear, Quartus doesn't automatically detect the ports of the top. I was tricked by the Pin Planner showing the IO STD of the pins without running any compilation step.

I haven't tested to add a location assignment to a port that doesn't exist in the top but I guess it'd have given me errors only after a compilation step.

Thanks @sstrell !

And thanks @ShengN_Intel for the help!