Stats

  • Locked Locked
  • Replies 4
  • Subscribers 126
  • Views 14821
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ASSURA RCX | capgen error

pitter

 Hi,

 After successful DRC and LVS verification RCX (C extraxtion) fails with the following error:

*ERROR* at "capgen": -res_blocking mask layer 'rblock_poly1' not defined in LVS file
quitting.

I have set the correct technology, the variable netlisting_mode is set to Analog. I also tried another extraction type, and always end up with the above error.

 Might be helpful (comes after error line in the logfile):

Forking:  /home/piter/Cadence/DiskExt/Assura/tools/assura/bin/32bit/capgen -substrate_stamping_off -techdir /home/piter/Cadence/HitKit/assura/c35b4/c35b4c3/RCX-typical -lvs /home/piter/Cadence/DiskExt/CadenceDesigns/LC_Test/ASSURA_LVS/INV_LayTest/LVS_A.xcn -p2lvs /home/piter/Cadence/HitKit/assura/c35b4/c35b4c3/RCX-typical/p2lvsfile -length_units meters -cap_unit 1.0 -selected_paths_proper -p poly1,capgen_gate,diffusion -no_cap_correction -cap_ground_layer net_psub -dsub net_nwell,net_psub -lexclude poly2,poly1 -blocking CPOLY_PSUB_device:1.8,poly2,poly1 -blocking CPOLY_NTUB_device:1.8,poly2,poly1 -blocking CPOLYRF_device,met1,poly2,poly1,diffusion,fox -blocking CMIM_device:1,met2cap,met2 -blocking RPOLY2RF_device,met1,poly2,poly1,diffusion,fox -blocking NMOSRF_device,met1,poly1,diffusion,fox -blocking PMOSRF_device,met1,poly1,diffusion,fox -res_blocking rblock_poly1,net_poly1 -res_blocking rblock_poly2,net_poly2 -res_blocking rblock_met1,net_met1 -res_blocking rblock_met2,net_met2 -res_blocking rblock_met3,net_met3 -res_blocking rblock_met4,net_met4 -sw3d /home/piter/Cadence/DiskExt/CadenceDesigns/LC_Test/ASSURA_LVS/INV_LayTest/LVS_A
*WARNING* Bad return status from RCX script generator. 0x100

 Any suggestions how to tacke the problem... thanks in advance!

 Kind Regards.

 

Parents
  • archive

     Assuming you're using a recent version of the AMS design kit, you need to run LVS as normal to verify connectivity and then rerun LVS with the "resimulate_extracted" switch set prior to running RCX.

     This is covered in the AMS documentation at  http://asic.austriamicrosystems.com/hitkit/hk400/assura/assura_rcx.html

     Cheers,

     Roger

Reply
  • archive

     Assuming you're using a recent version of the AMS design kit, you need to run LVS as normal to verify connectivity and then rerun LVS with the "resimulate_extracted" switch set prior to running RCX.

     This is covered in the AMS documentation at  http://asic.austriamicrosystems.com/hitkit/hk400/assura/assura_rcx.html

     Cheers,

     Roger

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.