Hi, one strange observation I find after using the input drivers in the harness, is the non-monotonicity in index1 data. Take a look at this (in the generated .lib file) : cell_rise (delay_template_7x7_1043) { index_1 (" 0.0294363, 0.029438, 0.0293399 , 0.0305652, 0.0330034, 0.0368964, 0.0424564"); index_2 ("0.001, 0.0017421, 0.00434703, 0.00932152, 0.0170715, 0.0279457, 0.0422546"); values ( \ "0.107349, 0.107349, 0.107349, 0.107349, 0.107349, 0.107349, 0.107349", \ "0.107465, 0.107465, 0.107465, 0.107465, 0.107465, 0.107465, 0.107465", \ "0.107164, 0.107164, 0.107164, 0.107164, 0.107164, 0.107164, 0.107164", \ "0.106852, 0.106852, 0.106852, 0.106852, 0.106852, 0.106852, 0.106852", \ "0.106702, 0.106702, 0.106702, 0.106702, 0.106702, 0.106702, 0.106702", \ "0.106364, 0.106364, 0.106364, 0.106364, 0.106364, 0.106364, 0.106364", \ "0.106601, 0.106601, 0.106601, 0.106601, 0.106601, 0.106601, 0.106601" \ ); } You can see that the 3rd value in the index 1 is smaller than previous two, so this violates the slew-load combinations intended for the cell modeling. What could possibly be the reason for this ? I don't find any errors i.e. Bad CCS data, and all the cells passing the characterization. However downstream tools complain about the values in the index1. Anuradha
↧