Stats

  • Replies 2
  • Subscribers 133
  • Views 140
  • Members are here 0

Schematic generation form spice file

VIRAJ PANCHAL

Hi everyone,

I am trying to generate schematic from spice(.spi) file through import spice option in virtuoso. But during schematic generation process I faced below error massage. 

*WARNING* (DB-270211): dbOpenCellViewByType: Cannot open cellview 'testLIB/DFCNQD1BWP6TSA16P96CPD/schematic' in 'a' mode because it does not exist or viewTypeName required to create a new cellview is not specified. Ensure that the cellview exists or to create a new cellview by specifying viewTypeName. Valid values for viewTypeName are "netlist", "schematic", "schematicSymbol" and "maskLayout".

According to above screenshot, The schematic view is not found in testLIB library. But how does it found before the schematic generation..!!??  It only give the netlist_tmp (blank schematic) as output but it should be schematic as output file. 

Kindly anyone tell me what's the issue.!?

Parents
  • AVAQ Semi

    The error message is actually a bit misleading. It is not saying that the schematic already exists and then disappears. It is saying that Virtuoso failed to create the schematic cellview.

    DB-270211 is typically generated when dbOpenCellViewByType() is called without a valid viewTypeName while trying to create a new cellview. For a new schematic, the view type must be "schematic"; otherwise Virtuoso cannot create testLIB/<cell>/schematic and only temporary data (such as netlist_tmp) may be left behind. This is expected behavior when the import process aborts.

    A few things I would check:

    • Verify that File → Import → Spice is configured to generate a schematic view rather than only a netlist.
    • Check the spiceIn.log file instead of only the CIW output. The first error in the log is usually the real cause.
    • Make sure your target library is writable and is an OA library.
    • If the netlist contains standard cells or custom devices, verify that the reference libraries and device mapping file are correctly specified. Missing mappings often cause the import to terminate before schematic generation completes.
Reply
  • AVAQ Semi

    The error message is actually a bit misleading. It is not saying that the schematic already exists and then disappears. It is saying that Virtuoso failed to create the schematic cellview.

    DB-270211 is typically generated when dbOpenCellViewByType() is called without a valid viewTypeName while trying to create a new cellview. For a new schematic, the view type must be "schematic"; otherwise Virtuoso cannot create testLIB/<cell>/schematic and only temporary data (such as netlist_tmp) may be left behind. This is expected behavior when the import process aborts.

    A few things I would check:

    • Verify that File → Import → Spice is configured to generate a schematic view rather than only a netlist.
    • Check the spiceIn.log file instead of only the CIW output. The first error in the log is usually the real cause.
    • Make sure your target library is writable and is an OA library.
    • If the netlist contains standard cells or custom devices, verify that the reference libraries and device mapping file are correctly specified. Missing mappings often cause the import to terminate before schematic generation completes.
Children
  • VIRAJ PANCHAL
    in reply to AVAQ Semi

    Thanks for your suggestion, 

    Ya the error message I understood, so do I change viewTypeName as schematic in anywhere in skill or dB files..? 

    I have checked my spice file and library(it has writable permission); both are proper. 

    I have give the reference libraries analogLib, basic, sample and <maintechLib>( in this case it is "cds_ff_mpt"). And I think no need for device mapping file, it should work with device map file. (I already cross checked in cadence RAK).

    I have attached my spi file as well as spiceIn log file. In spiceIn log file there is no information in last line. !! I thick it is incomplete. 

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.