Stats

  • State Not Answered
  • Replies 2
  • Subscribers 42
  • Views 754
  • Members are here 0
More Content

Back annotation via a TCL Script

Maxime1998

Hello everyone,

I’m currently trying to perform back annotation using a TCL script. I have identified the four commands used for back annotation, but I’m not able to apply the changes to my schematic.

I believe I need to use the “update schematic” step, but I would like to execute it via a command in my TCL script. Does anyone know the command or function to directly perform “update schematic” within a TCL script?

Thanks in advance,
Maxime

Parents
  • CadAP
    0

     

    Can you share those four commands?

    Meanwhile you can try the below command:

    pstswp.exe -pst -d <designName> -n <allegroDirectory> -c <configFIll Path> -v 3 -l 31 -s "" -j <FootPrintProperty> -hpath "HPathForCollision"

    Here

     -d :- to choose the Capture design file.

     -n :- to select the netlist directory.

     -s :- To select path for saving swp file.

     -c :- Allegro.cfg is the configuration file. One of the file available from .zip file.

    Hope it helps.

  • Maxime1998
    0 in reply to CadAP

    Yes, here are those command:


    exec "C:/Cadence/SPB_17.4/tools/bin/genfeedformat.exe" -x -b $rep_board -o $rep_schema
    puts "Extract logic from board"

    exec "C:/Cadence/SPB_17.4/tools/bin/pstswp.exe" -pst -d $rep_dsn -n $rep_schema -c "C:/Cadence/SPB_17.4/tools/capture/allegro.cfg" -v 3 -w -l 255 -s "" -j "PCB Footprint" -hpath "HPathForCollision" -backwd
    puts "Netlisting the design"

    exec "C:/Cadence/SPB_17.4/tools/bin/pstswp.exe" -swp -d $rep_dsn -n $rep_schema -s $rep_swp -c "C:/Cadence/SPB_17.4/tools/capture/allegro.cfg" -hpath "HPathForCollision" -backwd
    puts "generating backannotation file"

    exec "C:/Cadence/SPB_17.4/tools/bin/cmfeedback.exe" -overwrite -rZ $rep_xml physical in $rep_DCF $rep_cmdbview
    puts "Extracting Constraint Changes"

    These are the commands that appear in the session log. I can see that they detect the differences, but they don’t make any changes in my design. One of them looks similar to the command you gave me, but from what I understand, the third command is supposed to generate the .swp file.

    Than you very much,
    Maxime.

Reply
  • Maxime1998
    0 in reply to CadAP

    Yes, here are those command:


    exec "C:/Cadence/SPB_17.4/tools/bin/genfeedformat.exe" -x -b $rep_board -o $rep_schema
    puts "Extract logic from board"

    exec "C:/Cadence/SPB_17.4/tools/bin/pstswp.exe" -pst -d $rep_dsn -n $rep_schema -c "C:/Cadence/SPB_17.4/tools/capture/allegro.cfg" -v 3 -w -l 255 -s "" -j "PCB Footprint" -hpath "HPathForCollision" -backwd
    puts "Netlisting the design"

    exec "C:/Cadence/SPB_17.4/tools/bin/pstswp.exe" -swp -d $rep_dsn -n $rep_schema -s $rep_swp -c "C:/Cadence/SPB_17.4/tools/capture/allegro.cfg" -hpath "HPathForCollision" -backwd
    puts "generating backannotation file"

    exec "C:/Cadence/SPB_17.4/tools/bin/cmfeedback.exe" -overwrite -rZ $rep_xml physical in $rep_DCF $rep_cmdbview
    puts "Extracting Constraint Changes"

    These are the commands that appear in the session log. I can see that they detect the differences, but they don’t make any changes in my design. One of them looks similar to the command you gave me, but from what I understand, the third command is supposed to generate the .swp file.

    Than you very much,
    Maxime.

Children
No Data
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.