Stats

  • Locked Locked
  • Replies 3
  • Subscribers 142
  • Views 3116
  • 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

fprintf() works before run() but not after

FormerMember
FormerMember

There must be some peculiarity with our tools setup but if a file is created with file=outfile("filename") then i can write to a file until a run() statement is encountered. Any fprintf() after the run() gives error;

 ocean> *Error* fprintf: argument #1 should be an I/O port (type template = "ptg") - "/user/xxxxxxxxxxxxxxxxx/LIB/skill/ArtistKitNetlister.al"

xxxxx - some path

IC6.17-64b.500.21

spectre sub-version 17.1.0.270.isr5

  • Andrew Beckett

    A bit of a wild guess, based on what's happened. It would appear that you're using the ST "ArtistKit" integration as part of their "Unicad" environment. My guess is that some trigger code as part of this environment is setting a variable called "file" which has been accidentally left out of the let(), and consequently it is clobbering your variable called "file".

    You should report this to ST (I will mention it to my contacts in the team that develops this code), but in the meantime if you change your variable name containing the output port from "file" to something more unique I suspect the problem will go away.

    Regards,

    Andrew.

  • FormerMember
    FormerMember in reply to Andrew Beckett

    Thank you Andrew, you are exactly right! This is the only lateral thinking i had not thought of! Not using "file" works!

  • Andrew Beckett
    in reply to FormerMember

    Just a quick followup - my contact has identified some likely places where this may be happening, and is going to correct the code in the ArtistKit package so this should be solved in a future release.

    Kind Regards,

    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.