HI, I'm trying to perform PEX using QRC (EXT10.1) for a small custom design created in Virtuoso (IC6.1.5) using a commercial PDK. I've been following the guide that came with the PDK for performing DRC, LVS, PEX. It has passed DRC and LVS fine using Mentor Calibre (2011.4) however I get the following error in the QRC log:
#==========================================================## Flatten net file, routing, via and device layers#==========================================================#SAVEDIR=`beginFlattenInputs`export SAVEDIR/bin/mv -f NET h_NETflatnet -V -li -h '/' h_NET NETflatnet took 0.00 user, 0.00 sys, 0.00 elapsed, 5884.0 kbytesnetprint -V -N1 power_list:power_list_nums NETflattenTransistorData \<ENCRYPTED_0LAYER_06154\>-118 meterssh: ENCRYPTED_0LAYER_06154: No such file or directorysh: ENCRYPTED_0LAYER_06154: No such file or directoryERROR (FLTTDTA-109002): Forked flattub command failed.ERROR (LBRCXM-609): Bad return status from RCX run. 0xff00INFO (LBRCXM-709): ***** QRC terminated abnormally *****
Has anyone come across a similar error before or could suggest anything to try?
Many thanks in advance for your help.
You didn't mention what you're using for the LVS step prior to QRC. Are you using Calibre LVS with QRC, Assura LVS with QRC or PVS with QRC?
Anyway, I did a quick search and couldn't find anything that was quite like what you're reporting, There were some fixes in an EXT10.1 hotfix, so it might be worth checking you have the latest hotfix (I'm not sure it's quite the same issue though), but other than that I'd suggest going via customer support; that's what it's for!
Thanks for the quick response Andrew.
I'm using Calibre for LVS as well as Calibre for DRC, as this is what the PDK specifies. I'm then performing a calibre query before using QRC for the extraction.
I'm already using a hotfix version of EXT 10.1 (EXT_10.12HF123). I might be mistaken but I don't think we qualify for any further updates or customer support direct from cadence, as we got the tools and support from Europractice.
OK, but you can still report this to Europractice, and they in turn will contact us (Cadence) if necessary (quite likely to be necessary in this case). That's the best bet.
The fact that it's talking about a layer called "ENCRYPTED_LAYER0..." might give a clue, but that might just be a name chosen in the LVS rules, so not sure. There are others in Cadence who have a more in-depth knowledge of this flow than I do, so I'd defer to them - and that's another good reason to go via customer support, even if indirectly as you're from a University.
I've already been in contact with Europractice about the problem and they suggested trying EXT10.1 instead of EXT9.1, which I now have. I'll get back in contact with them and see if they can contact cadence customer support as you suggested.
Many thanks again for your help and I'll post back if a solution is found.