Just to recap: say we have a design instance hierarchy - Top | Middle | ------------- | | | | D1 R1 D2 R2 Say modules D1 and D2 have drivers and R1 and R2 receivers on the same net, so connect modules will be inserted. If the module "middle" routes power differently to D1 and D2 (e.g. some power gating) then you want the auto inserted module to pick up Vdd (say) for the D1 D2A in D1 and the D2 D2A in D2. The module "middle" may have a signal Vdd coming from top but will explicitly feed a gated (say) VddD1 to D1.Vdd and VddD2 to D2.Vdd. If the connect modules are instantiated in "middle" then a hierarchical upward search for "Vdd" will find the feed from top not the feed to D1 or D2. It is therefore desirable that the D2As are instantiated on the down side of the ports they are associated with, otherwise the search algorithm for hooking up "inherited" signals isn't going to be the same for regular and connect module instances (if it is going to work correctly). Kev. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Fri Mar 23 10:38:57 2007
This archive was generated by hypermail 2.1.8 : Fri Mar 23 2007 - 10:39:09 PDT