Stats

  • Locked Locked
  • Replies 4
  • Subscribers 64
  • Views 14573
  • 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

coverage on e Temporal checks

jaichandra

Hi

    I am trying to get functional coverage on the temporal checks in my e based verification environment. I added the  specman_pre_command "configure cover -collect_checks_expects=TRUE" in my simulation script. I also have the specman_pre_command "configure cover -specview_cover_window" to view the old specman coverage window. My queries are

 1. I read somewhere that temporal expression coverage can be collected  only with IMC tool.Is it true. In my current setup with collect_checks_expects variable i am not able to see th TC coverage where as i am able to see other coverage blocks.

 2. I tried to get coverage DB in IMC format with "-coverage block:functional" in the ncelab phase. After running the simulation icc_<des_csum>_<ver_csum>.ucm file is generated for code coverage but sn_<des_csum>_<ver_csum>.ucm is not generated for functional coverage. And the functioanl coverage ucd file is generated as sn.ucd instead of sn_<>_<>.ucd. For code coverage the ucd file is generated in the icc_<>_<>.ucd format.

   Any help in resolving this issue if greatly appreciated.  

 

  • Hi,

    regarding your questions:
    1. the collection of checks and expects is controlled by the option you use. The results are stored in the coverage database
        However, as you found out, the old coverage viewer in Specview doens't show those results, they can only be seen in IMC

    2. when specmans runs under vManager, it automatically creates a coverage model. If Specman only runs stand alone, or with a
       simulator, you need to enable model dmuping by setting the following: set_config(cover,write_model,ucm) . The elab option you
       passed only affects the simulator, and not specman

    Regards,
    -hannes 

  • Hi hannes,

             Thanks for your reply. I found the source of my issue. In my simulation environment, i compile my e-code and create an executable file for IES, with which i load my testcase and run the simulation. I compile the ecode using the sn_compile.sh. when i use the "set_config(cover,collect_checks_expects,TRUE);" with -p option for specrun command along with the executable file to run simulation i get  "ERR_COV_EXPECT_AFTER_LOAD" error. If i remove the above "set_config" for Temporal expression coverage the simulations works fine and dumps the functional coverage for specman cover blocks. How can i include "set_config(cover,collect_checks_expects,TRUE);" command during my e-code compilation with sn_compile.sh command.

       When i am loading the full ecode, with above set_config command i am able to get coverage on my temporal expressions. But i want to use the compiled executable to run the regression without loading the full ecode env for every run.

     

  • To pass such setting to sn_compile.sh you can set the SPECMAN_PRE_COMMANDS environment variable, e.g:
    setenv SPECMAN_PRE_COMMANDS "set_config(cover,collect_checks_expects,TRUE)
    sn_compile.sh <your arguments>


    This will pass the command to Specman before the code is loaded, translated and compiled.

    -hannes 

  • Hi hannes,

            Thanks for your reply. I found the issue and resolved it. Actually i did set the SPECMAN_PRE_COMMANDS variable with set_config(cover,collect_checks_expects,TRUE) command but i was overwritting it in another file. Once i fix this, my issue is resolved. Thanks a lot for you help. Have a nice day.

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.