Fail to run with user defined the "connect rules"

Hi Yi,

The best thing to do would be log this as a case with customer support (I assume there's a good reason why you're using IC616 (an unsupported release) too, although I suspect this is just a setup issue rather than related to the specific version because this bit hasn't changed for some time as far as I know).

The reason why I think a case makes more sense as then you can share your connectRules.il file so that one of the team can check it.

Regards,

Andrew.

Hi Andrew

Happy new year.

Thank you for your quick reply. 

The reason that 616 is used, simply because the project environment is setup by another guy. I am pushing him to move to the latest version of cadence.

I will try it out in 617 in a local CADENV, if the failure is still exist, I will file a case in the customer support.

For me it's sufficient to know the script for connect rules remains the same for a long time.

Best Regards

Yi

Hi Andrew

I have tried it in 617, still the same issue.

But with 617, I can use IE card, and by clicking the link of the connect module in the CR file, such warning message pops up in the CIW

"*WARNING* File "/home/ceres_ns/cadenv/cadenv_default/.caddata/cadence_incisive/tools/affirma_ams/etc/connect_lib/connectLib/Bidir_simvsup/module/verilog.vams" does not exist"

It seems that the location of my own connect library is not used. But default cadence connect library location is used to point the module.

Thus in the AMS simulation, no corresponding connect module is found.

I have gone through the connectRule.il file and tutorial once again, but still I do not find anything to define the path for the connect module.

For me this is the missing piece to introduce customized connection rules.

I have contacted the local Cadence support engineer. Hopefully he can guide me to find the correct setup.

If you have a quick answer, it's always welcome.

Best Regards

Yi

Hi Yi,

Without working through this again, and comparing with what you've done, I'm not sure I can offer much advice. I've done this before and don't recall there being such an issue, but I'd have to put aside the time to work through it. 

Let's see if you can get this resolved with the local support AE first, and then we can take it from there if needed (he can always loop me in if needed).

Regards,

Andrew.

Hi Andrew

My colleague helps me find the root cause.

When I generate the connectRules.il by using the genConnRulesFile command, I only put the .vams file for the rule definition in the -lib argument.

As I only consider this one as the connect rule file, the others are for the connect modules.

I am little bit misled by the tutorial. (it's the document in 6.1.6)

On the other hand, when I search the Cadence Doc again in the 6.1.7, in the Q&A part, I do find the right description for compiling the user connect rules, as:

So, it's not only we should use the latest version of Cadence, but also we should look at the latest document

Best Regards

Yi

Yi,

Glad it's resolved! Thanks for feeding back the solution too so that others can learn from it.

Regards,

Andrew.