Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 13008
  • 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

Forcing Encounter to run specific command in specific shell

LA2405x

Hi all,

We are using Encounter Foundation Flow to design our digital blocks.
It works good so far, but we had some struggles with the foundrys delivered hotcode/tech files.
After closing on these, we still got stuck with issues the foundry support could not help us:

The flow runs ok so far, until at the end at extractRC command, we get:

...
Exit code 0.
Cadence Quantus QRC Extraction completed successfully at 2017-Jul-26
15:12:44 (2017-Jul-26 13:12:44 GMT).
sh: 1: Syntax error: Bad fd number
sh: 1: Syntax error: Bad fd number

And the job is stuck there.
We were looking for quite a while now, but could not resolve it, neither we really got to the point to know what actually happened.

Is there a chance to run a very verbose flow, to see what happened? Or something where we can add "breakpoints", or specific commands while executing FF, to check what happens?
Or is the solution maybe quick and simple and you know it?

Please let us know what you think about it!

Thank you very much,
Adrian

Parents
  • Ok, just as I posted the question, we found the answer (like we were looking for two weeks for it :| )
    The fix was quite simple - We changed the symlink of sh (/bin/sh) from /bin/dash to /bin/bash -> FIX!

    I hope this helps if others have the same issue.
Reply
  • Ok, just as I posted the question, we found the answer (like we were looking for two weeks for it :| )
    The fix was quite simple - We changed the symlink of sh (/bin/sh) from /bin/dash to /bin/bash -> FIX!

    I hope this helps if others have the same issue.
Children
No Data

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.