Stats

  • Locked Locked
  • Replies 6
  • Subscribers 92
  • Views 14949
  • 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

More problems with Encounter Library Characterizer (ELC)

RungBin
Hi, I run into more problems with ELC when executing db_prepare. The spice library file (coming from TSMC) which I used for ELC is no problem with hspice, but I run into the following problem while executing db_prepare. My previous problem posted on August 15 was using a spice library file whose subckt keywords are commented out. Hence, I am wondering whether ELC can deal with a subckt definition within a .LIB section in a SPICE library file. I am more curious about whether anyone else is using ELC. Thanks for your help. Best regards, Rung-Bin - including rf018.l : RF_MOS Reading SUBCKT:NMOS_RF Reading SUBCKT:PMOS_RF - including rf018.l : MOS_RF - including rf018.l : DIO_RF - including rf018.l : RF_MOS Reading SUBCKT:NMOS_RF [ERROR(db_prepare)] spice syntax error: NMOS_RF : redefinition of the subckt [ file = rf018.l, #line = 1552 ] => .SUBCKT nmos_rf D G S B lr=18.E-08 nr=64 wr=1.5E-6
Parents

  •  

    Dear Julian, Thank you so much. Your suggestion works when I do not include the following line in modelspice.sp because my hspice simulator can not recognize it. simulator lang=spice However, I found that ELC just does not produce data for internal fall_power in the output library file out.lib. Below are the internal power data produced by ELC. Do you have the same problem? Is there a solution for this? Looking forward to hearing from you. Thanks again.

    Best regards, Rung-Bin

    internal_power() { related_pin : "B"; when : "A";

    rise_power(energy_template_7x7) { index_1 ("0.03, 0.1, 0.4, 0.9, 1.5, 2.2, 3"); index_2 ("0.00035, 0.021, 0.0385, 0.084, 0.147, 0.231, 0.3115"); values ( \ "0.00115, 0.067566, 0.124174, 0.271881, 0.475576, 0.74728, 1.00608", \ "0.001161, 0.067696, 0.124546, 0.271154, 0.476156, 0.748399, 1.00174", \ "0.001075, 0.06688, 0.123424, 0.271997, 0.476142, 0.74833, 1.00553", \ "0.001147, 0.067461, 0.124297, 0.269402, 0.47623, 0.748605, 1.00676", \ "0.001054, 0.067198, 0.124859, 0.272029, 0.47621, 0.748343, 1.00928", \ "0.001082, 0.067408, 0.124578, 0.2721, 0.476171, 0.748392, 0.993107", \ "0.001097, 0.067349, 0.123965, 0.271298, 0.476332, 0.748429, 1.00807"); }

    fall_power(energy_template_7x7) { index_1 ("0.03, 0.1, 0.4, 0.9, 1.5, 2.2, 3"); index_2 ("0.00035, 0.021, 0.0385, 0.084, 0.147, 0.231, 0.3115"); values ( \ "0, 0, 0, 0, 0, 0, 0", \ "0, 0, 0, 0, 0, 0, 0", \ "0, 0, 0, 0, 0, 0, 0", \ "0, 0, 0, 0, 0, 0, 0", \ "0, 0, 0, 0, 0, 0, 0", \ "0, 0, 0, 0, 0, 0, 0", \ "0, 0, 0, 0, 0, 0, 0"); }

Reply

  •  

    Dear Julian, Thank you so much. Your suggestion works when I do not include the following line in modelspice.sp because my hspice simulator can not recognize it. simulator lang=spice However, I found that ELC just does not produce data for internal fall_power in the output library file out.lib. Below are the internal power data produced by ELC. Do you have the same problem? Is there a solution for this? Looking forward to hearing from you. Thanks again.

    Best regards, Rung-Bin

    internal_power() { related_pin : "B"; when : "A";

    rise_power(energy_template_7x7) { index_1 ("0.03, 0.1, 0.4, 0.9, 1.5, 2.2, 3"); index_2 ("0.00035, 0.021, 0.0385, 0.084, 0.147, 0.231, 0.3115"); values ( \ "0.00115, 0.067566, 0.124174, 0.271881, 0.475576, 0.74728, 1.00608", \ "0.001161, 0.067696, 0.124546, 0.271154, 0.476156, 0.748399, 1.00174", \ "0.001075, 0.06688, 0.123424, 0.271997, 0.476142, 0.74833, 1.00553", \ "0.001147, 0.067461, 0.124297, 0.269402, 0.47623, 0.748605, 1.00676", \ "0.001054, 0.067198, 0.124859, 0.272029, 0.47621, 0.748343, 1.00928", \ "0.001082, 0.067408, 0.124578, 0.2721, 0.476171, 0.748392, 0.993107", \ "0.001097, 0.067349, 0.123965, 0.271298, 0.476332, 0.748429, 1.00807"); }

    fall_power(energy_template_7x7) { index_1 ("0.03, 0.1, 0.4, 0.9, 1.5, 2.2, 3"); index_2 ("0.00035, 0.021, 0.0385, 0.084, 0.147, 0.231, 0.3115"); values ( \ "0, 0, 0, 0, 0, 0, 0", \ "0, 0, 0, 0, 0, 0, 0", \ "0, 0, 0, 0, 0, 0, 0", \ "0, 0, 0, 0, 0, 0, 0", \ "0, 0, 0, 0, 0, 0, 0", \ "0, 0, 0, 0, 0, 0, 0", \ "0, 0, 0, 0, 0, 0, 0"); }

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.