Stats

  • Locked Locked
  • Replies 6
  • Subscribers 127
  • Views 3650
  • 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

Calibre(cal_2011.4_35.27) compatible with IC615?

Xiongliang

Dear Folks,

 

   We installed the Calibre (x86_cal_2011.4_35.27) on both 32-bit and 64-bit Linux machines with IC615 (IC-6.1.5-hf510). But it does not seem working properly. The calibre interface can be opened, but the DRC and RVE can not be run and showed the following errors:

 

 *Error* fprintf/sprintf: format spec. incompatible with data - "Format is '%s -hierDepth %s', argument #2 is 20"
<<< Stack Trace >>>
_sprintf("%s -hierDepth %s" strm_cmd (streamOutKeys->hierDepth))
(strm_cmd = _sprintf("%s -hierDepth %s" strm_cmd (streamOutKeys->hierDepth)))
sprintf(strm_cmd "%s -hierDepth %s" strm_cmd (streamOutKeys->hierDepth))
when(((streamOutKeys->

hierDepth) && ((streamOutKeys->hierDepth) != "")) sprintf(strm_cmd "%s -hierDepth %s" strm_cmd (streamOutKeys->hierDepth)))
let((strm_cmd tf) sprintf(nil "%L%L%L%L" libName cellName viewName ... ) (strm_cmd = strcat("strmout -library '" (streamOutKeys->libName) "'" " -strmFile " (streamOutKeys->outFile) ... )) unless(((streamOutKeys->cellMapTable) == "") (strm_cmd = strcat(strm_cmd " -cellMap " &))) unless(((streamOutKeys->layerTable) == "") (strm_cmd = strcat(strm_cmd " -layerMap " &))) ... )
mgc_rve_export_get_oastream_cmd(libName cellName viewName fileName)
(cmd = mgc_rve_export_get_oastream_cmd(libName cellName viewName fileName))

 

   Has anyone met the same problem?

 

Regards,

Parents

  • Hello.

    This problem can be addressed by making a couple of minor changes to the file mgc_export.skl which is found in the mentor/calibre tree.  In that file, you will see the format strings being used to process hierDepth and maxVertices (they both will fail, but the stack trace occurs on the first failure).

    Using Andrew's suggestion, we first determined what streamOutKeys-hierDepth is being set to - string or decimal.  They we alter the format string to match.  Same for maxVertices.

    Exercise care, especially if you are in a multi-version environment.  At some point in the past, we edited our file to expect decimals, and now we have to undo it.  It seems different IC or Calibre sub-versions may have built streamOutKeys differently.  I am not sure which tool actually builds that data structure.

    Good Luck

    Todd

Reply

  • Hello.

    This problem can be addressed by making a couple of minor changes to the file mgc_export.skl which is found in the mentor/calibre tree.  In that file, you will see the format strings being used to process hierDepth and maxVertices (they both will fail, but the stack trace occurs on the first failure).

    Using Andrew's suggestion, we first determined what streamOutKeys-hierDepth is being set to - string or decimal.  They we alter the format string to match.  Same for maxVertices.

    Exercise care, especially if you are in a multi-version environment.  At some point in the past, we edited our file to expect decimals, and now we have to undo it.  It seems different IC or Calibre sub-versions may have built streamOutKeys differently.  I am not sure which tool actually builds that data structure.

    Good Luck

    Todd

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.