Stats

  • Locked Locked
  • Replies 5
  • Subscribers 67
  • Views 14240
  • 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

OCEAN script Problem

stevenLiu

Hi all,

 When I was using "load" command to run OCEAN script for simulating an LNA netlist, the following error came out:

 *Error* ilGetString: arg must be symbol or string - nil

 I am a starter and hope any one give a help.

 

Zheng

 

Parents

  • Hi Steven,

     One suggestion I can make is to insert debug messages at various locations, something like the following:

    fprintf(stderr "DEBUG1: before foreach\n") ;;debug

    foreach( sweepVariable resistorList
        fprintf(stderr "DEBUG2: before parametric analysis\n") ;;debug

         paramAnalysis(sweepVariable ?start startPoint ?stop stopPoint ?lin totalPoints)

        fprintf(stderr "DEBUG3: before S parameter analysis setup\n") ;;debug

          ;S-Parameter analysis
             analysis('sp ?ports list("/PORT1" "/PORT2")  ?start "400M"  ?stop "8G" 
            ?lin "601"  ?donoise "yes"  ?oprobe "/PORT2"  ?iprobe "/PORT1"  )
     ...


    This way you can get useful information as to where the problem is arising; once the offending code has been isolated, it will be easier to track down and debug the cause.  By putting DEBUG in the print output and "debug" in the comment you have two chances to find these statements later when they need to be removed.

    I hope that this helps you to find and solve the problem.

    Regards,

    Lawrence.

Reply

  • Hi Steven,

     One suggestion I can make is to insert debug messages at various locations, something like the following:

    fprintf(stderr "DEBUG1: before foreach\n") ;;debug

    foreach( sweepVariable resistorList
        fprintf(stderr "DEBUG2: before parametric analysis\n") ;;debug

         paramAnalysis(sweepVariable ?start startPoint ?stop stopPoint ?lin totalPoints)

        fprintf(stderr "DEBUG3: before S parameter analysis setup\n") ;;debug

          ;S-Parameter analysis
             analysis('sp ?ports list("/PORT1" "/PORT2")  ?start "400M"  ?stop "8G" 
            ?lin "601"  ?donoise "yes"  ?oprobe "/PORT2"  ?iprobe "/PORT1"  )
     ...


    This way you can get useful information as to where the problem is arising; once the offending code has been isolated, it will be easier to track down and debug the cause.  By putting DEBUG in the print output and "debug" in the comment you have two chances to find these statements later when they need to be removed.

    I hope that this helps you to find and solve the problem.

    Regards,

    Lawrence.

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.