Stats

  • State Not Answered
  • Replies 1
  • Subscribers 159
  • Views 6616
  • Members are here 0
More Content

Run dev_check on device file for more information.

Ram1234

Hi Team,

Good day!

How to run the Run dev_check, 

where can I find this option and how do I run it?

Please help me to fix this error.

"" Pin numbers do not match between symbol and component. Run dev_check on device file for more information.",

I know this error is because the symbol and footprint pins are not matched.

To find the error, we need to run the dev_check, so please help me find the procedure to fix.

Thanks, 

  • 0

    Hi Ram,

    You should see these errors while creating or importing netlist. Check below information:

    The dev check batch command that compares device files and package symbol definitions and generates a log file listing any discrepancies.

    This command automatically:

    • Checks the syntax of the device files specified in the command.
    • Creates a temporary netlist called dev_check.net, which consists of the $PACKAGES section of the netlist file.
      The dev_check.net file contains no information and is used only to check symbols against the device files. The $PACKAGES file section creates U1, U2, U3 and so on, sequentially.
      The dev_check command creates a temporary drawing called dev_check.brd and runs the netin command, which loads a $PACKAGES section of a netlist into the drawing so that the editor can check the devices and symbols in the drawing.
    • Creates a dev_check.log file which contains a netin.log.
    • Identifies any errors as listed in the netin.log and displays them on the screen.

    Ensure that your environment path points to the proper directories for padstack files (PADPATH), device files (DEVPATH), and symbol files (PSMPATH) so that the tool can access the correct padstacks, devices, and package symbols.

    
dev_check [-version] <device_filename>.txt
Cadence Guidelines

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.