Stats

  • Replies 10
  • Subscribers 161
  • Views 5485
  • Members are here 0
More Content

netrev.exe crashes when attempting to update BRD file (17.2)D

l3hrbonini

I have a design in Capture CIS that will netlist without issue.  When I try to update the PCB, pst files get created and then a windows dialog pops up stating that "nextrev.exe has stopped working".  When I try to do an Import>Logic from PCB editor, it completes with warnings/errors, and the log stops at "preparing to read pst files" with no additonal information.  I'm thinking that netrev is crashing at the same point there as well.

Obivously that's not a lof of information to go on, so any suggestion that might at least point me in the right direction as to why netrev crashes and the BRD won't update would be helpful.

  • Delete the .pst files existing in outputs. File-save as and rename design. Make sure there are no illegal characters in the file path or name. This should help.

  • in reply to AvengerThanos

    Thanks for the suggestion.  Is there a list of illegal characters documented somewhere?

  • I tried AvengerThanos' suggestion, copied both the .DSN and .BRD to a temporary folder on the desktop and renamed them.  I get the same result.  Here's the entire session log output after the netlist completes:

     

    ********************************************************************************
    *
    * Updating Allegro PCB Editor Board
    *
    ********************************************************************************
    INFO(ORCAP-32040): Updating Allegro PCB Editor Board


    Spawning... netrev.exe -y 1 -i "C:\USERS\RBONINI\DESKTOP\TEST\allegro" "C:\Users\rbonini\Desktop\test\223023_PCB.brd" "C:\Users\rbonini\Desktop\test\223023_PCB.brd"
    Reading File : C:/USERS/RBONINI/DESKTOP/TEST/allegro/pstchip.dat
    (00:00:00.04)
    Reading File : C:/USERS/RBONINI/DESKTOP/TEST/allegro/pstxprt.dat
    (00:00:00.03)
    Reading File : C:/USERS/RBONINI/DESKTOP/TEST/allegro/pstxnet.dat

    Exiting... netrev.exe -y 1 -i "C:\USERS\RBONINI\DESKTOP\TEST\allegro" "C:\Users\rbonini\Desktop\test\223023_PCB.brd" "C:\Users\rbonini\Desktop\test\223023_PCB.brd"
    (---------------------------------------------------------------------)
    ( )
    ( Allegro Netrev Import Logic CmdLine: netrev.exe -y 1 -i C:\USERS\RBONINI\DESKTOP\TEST\allegro C:\Users\rbonini\Desktop\test\223023_PCB.brd C:\Users\rbonini\Desktop\test\223023_PCB.brd

    ------ Preparing to read pst files ------

    INFO(ORCAP-32005): *** Done ***
    )
    ( )
    ( Drawing : 223023_PCB.brd )
    ( Software Version : 17.2P019 )
    ( Date/Time : Thu May 21 09:53:08 2020 )
    ( )
    (---------------------------------------------------------------------)


    ------ Directives ------------

    Ripup etch: No
    Ripup delete first segment: No
    Ripup retain bondwire: No
    Ripup symbols: Always
    Missing symbol has error: No
    DRC update: Yes
    Schematic directory: 'C:\USERS\RBONINI\DESKTOP\TEST\allegro'
    Design Directory: 'C:/Users/rbonini/Desktop/test'
    Old design name: 'C:/Users/rbonini/Desktop/test/223023_PCB.brd'
    New design name: 'C:/Users/rbonini/Desktop/test/223023_PCB.brd

  • in reply to l3hrbonini

    There should be a netrev.log file, either in the project folder, or the Allegro (pstxxx.dat files location) folder. What does it say? I'll always get a log file, even when it doesn't complete because of errors.

  • in reply to l3hrbonini

    Btw - do you have the .brd file open when you're trying to import?

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.