Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 15591
  • 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

QRC Extraction

soha

Hi,

I am using Assura 4.1 USR4 HF1 and EXT 14.10. I am planing to measure delay; thus, I need to create a SPEF File. I am trying to run the QRC extraction, but I get the following error.  I have the same issue running on EXT , and even invoking it from EDI. Could you please help me to solve this error. 

INFO (EXTGRMP-102) : Starting at 2016-Apr-13 22:40:48 (2016-Apr-14 03:40:48 GMT).
Running binary as:
/usr/local/cds2008/ext/tools/extraction/bin/64bit/qrc -cmd
./__qrc.spefOutput.ccl -multi_cpu 8 ./gscl45nm.lef

INFO (EXTHPY-168) : Input stage started at Wed Apr 13 22:40:48 2016.
Path/Simulation/EXT_TSV/./.dpw.17359.100000.exe: line 9: syntax error near unexpected token `='() { eval `/usr/bin/modulecmd bash $*`
}''
Path/Simulation/EXT_TSV/./.dpw.17359.100000.exe: line 9: `}''
Path/Simulation/EXT_TSV/./.dpw.17359.100011.exe: line 9: syntax error near unexpected token `='() { eval `/usr/bin/modulecmd bash $*`
}''
Path/Simulation/EXT_TSV/./.dpw.17359.100011.exe: line 9: `}''
Path/Simulation/EXT_TSV/./.dpw.17359.100022.exe: line 9: syntax error near unexpected token `='() { eval `/usr/bin/modulecmd bash $*`
}''
Path/Simulation/EXT_TSV/./.dpw.17359.100022.exe: line 9: `}''

WARNING (EXTGRMP-103) : Request failed for resource: sh. Resource will be ignored.
Path/Simulation/EXT_TSV/./.dpw.17359.100033.exe: line 9: syntax error near unexpected token `='() { eval `/usr/bin/modulecmd bash $*`
}''
Path/Simulation/EXT_TSV/./.dpw.17359.100033.exe: line 9: `}''
Path/Simulation/EXT_TSV/./.dpw.17359.100044.exe: line 9: syntax error near unexpected token `='() { eval `/usr/bin/modulecmd bash $*`
}''
Path/Simulation/EXT_TSV/./.dpw.17359.100044.exe: line 9: `}''
Path/Simulation/EXT_TSV/./.dpw.17359.100055.exe: line 9: syntax error near unexpected token `='() { eval `/usr/bin/modulecmd bash $*`
}''
Path/Simulation/EXT_TSV/./.dpw.17359.100055.exe: line 9: `}''

WARNING (EXTGRMP-103) : Request failed for resource: sh. Resource will be ignored.

Thank you,

Soha

  • Andrew Beckett

    A similar question came up before in this thread. It looks like something wrong in your (and the other post's) environment that when trying to run "sh" it fails. What happens if you just run "sh" at the UNIX prompt?

    Maybe you are at the same organisation that posted the previous question?

    Andrew.

  • soha

    Thank you Mr. Andrew for your response. I did see the other question but there is no answer, that is why I submitted this question. I was trying to solve this problem for days. When I run "sh" at at the UNIX prompt, I got  "sh-4.1$". Could you please help me to solve this?

    Thanks,

  • Andrew Beckett

    I can't really help to solve this - I have no idea what might be the root cause and I've not found any reports of it anywhere (either in our internal databases or on the global web, other than the other post in the forums).

    The only thing I can suggest is for you to contact customer support via whatever is your usual channel - we'll need to take a detailed look at your setup to understand it, and that's not really viable via the community forums - you need the full customer support experience for that.

    Kind Regards,

    Andrew.

  • soha
    Thanks Andrew. I will contact the customer support. Moreover, I got another error which I do not understand.

    INFO (EXTGRMP-354) : There are no RCgen techfile data in the unified techfile. RCgen techfile
    data are necessary for QRC cell level extractions.
    ERROR (EXTGRMP-138) : Session cannot continue due to previously reported errors.

    Regards,
    Soha
  • Andrew Beckett

    Soha,

    This second message is covered in this COS article.

    Andrew.

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.