Using get_entity_instances properly in reusable sdc files

[RHenr]

Hello,
I would like to write reusable sdc exceptions for components that can be shared accross several projects.
The get_entity_instances command seems to be what I am looking for but I'm face issues with it, as I'm not a tcl expert.

I have started with something like this :

set myList [get_entity_instances -nowarn MyEntity]

foreach elem $myList {
  
  # This command is ok
  set_multicycle_path -from "$elem|myVect[0]" -to "$elem|mySignal" -setup 2
  
  # This command is wrong because curly braces prevent variable evaluation
  set_multicycle_path -from {$elem|myVect[*]} -to {$elem|mySignal} -setup 2

  # This command reports unmatching keeper/pin/etc
  set_multicycle_path -from "$elem|myVect[*]" -to "$elem|mySignal" -setup 2
}

My question is : how should I write these commands to use vectors ?

Thanks

Edit : it seems it was not working because my constraint had the first form :

# This constraint fails
set_multicycle_path -from "$elem|SUBMODULE:submodule|myVect[*]" -to "$elem|mySignal[*]" -hold 2
# This constraint is ok
set_multicycle_path -from "$elem|submodule|myVect[*]" -to "$elem|mySignal[*]" -hold 2

[RichardTanSY_Intel]

Is my understanding correct that you want to have a component that has its own SDC file so you can use it in multiple projects? Like an IP component that is able to generate its own SDC constraint.

Have you been able to solve the issue by yourself? It seems that you have the constraints working.

Best Regards,

Richard Tan

[RichardTanSY_Intel]

Dropping a note to ask if my last reply was helpful to you?

Do you need any further assistance from my side? 

Best Regards,

Richard Tan

p/s: If you find any answers from the community or Intel Support to be helpful, we encourage you to mark them as the best answer or rate them 4/5 in the survey. 

[RichardTanSY_Intel]

We noticed that we haven't received a response from you regarding the latest previous question/reply/answer, and will now transitioning your inquiry to our community support. We apologize for any inconvenience this may cause and we appreciate your understanding.

If you have any further questions or concerns, please don't hesitate to let us know. 

Thank you for reaching out to us!

Best Regards,

Richard Tan

p/s: If you find any answers from the community or Intel Support to be helpful, we encourage you to mark them as the best answer or rate them 4/5 in the survey.