• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. ISSUE: Merging coverage databases for more than 100 tes...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 65
  • Views 14953
  • 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

ISSUE: Merging coverage databases for more than 100 testcases

mahee424
mahee424 over 9 years ago

Hi,

      I've about 400 test cases to merge all the individual coverage data bases to one output file with use of IMC. I'm using below IMC version;

IMC(64): 14.10-s011: (c) Copyright 1995-2014 Cadence Design Systems Inc.

I've found the following error during merging process in BATCH MODE;
mydir> imc -batch
imc>merge mipi_base_test*/scope/mipi_base_test -out final -metrics all -initial_model union_all -message 1
imc>merge: too many arguments
imc>merge: usage: merge [-AeEpqxX3] [-L lab [-L lab [-L lab]]] file1 file2 file3
imc>merge aborted


even i tried giving all the individual test names but still giving the above error.

Can any one suggest me to merge all the 400 test cases?(for my case).

regards,

mahee

  • Cancel
Parents
  • StephenH
    StephenH over 9 years ago

    The number of tests is not your problem, I can do the same command here and it works.

    % imc -batch

    IMC(64): 14.10-s011: (c) Copyright 1995-2014 Cadence Design Systems Inc
    Starting batch mode
    imc> merge mipi_base_test*/scope/mipi_base_test -out final -metrics all -initial_model union_all -message 1
    *I,MERGL1: Merging IUS Coverage ...
    ----------------------------
    *I,MERGL1: Preparing target model ...
    *I,MERGL1: Doing model union ...
    *I,MERGL2: With primary run (mipi_base_test_01/scope/mipi_base_test): mipi_base_test_01/scope/icc_27f588a9_00000000.ucm
    *I,MERGL1: Target model generated successfully.
    *I,MERGL1: Projecting IUS ucd data into the target model ...
    *I,MERGL2: mipi_base_test_01/scope/mipi_base_test:
    *I,MERGL3: Merging instance tree tb to tb:
    *I,MERGL3: Data is projected in to the target model.
    *I,MERGL2: mipi_base_test_02/scope/mipi_base_test:
    *I,MERGL3: Merging instance tree tb to tb:
    *I,MERGL3: Data is projected in to the target model.
    *I,MERGL2: mipi_base_test_03/scope/mipi_base_test:
    *I,MERGL3: Merging instance tree tb to tb:
    *I,MERGL3: Data is projected in to the target model.
    *I,MERGL1: Writing output database cov_work/scope/final:
    *I,MERGL2: Model: cov_work/scope/final/icc_27f588a9_00000000.ucm
    *I,MERGL2: Data : cov_work/scope/final/icc_27f588a9_00000000.ucd
    *I,MERGL1: No Specman coverage databases found in the runs.
    Total conflicts during target model creation: 0
    Total items not merged : 0
    imc>

    So, I'm sure the problem is in your environment somehow. If you'd been pasting the command from an email or documentation, try typing it out manually, in case there are some hidden special characters screwing everything up.

    Please note that 14.10.011 is very old, it came out in early 2014, please consider using a newer version; the last 14.10 update was in May 2016, or you could look at using a supported version such as 15.20.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • StephenH
    StephenH over 9 years ago

    The number of tests is not your problem, I can do the same command here and it works.

    % imc -batch

    IMC(64): 14.10-s011: (c) Copyright 1995-2014 Cadence Design Systems Inc
    Starting batch mode
    imc> merge mipi_base_test*/scope/mipi_base_test -out final -metrics all -initial_model union_all -message 1
    *I,MERGL1: Merging IUS Coverage ...
    ----------------------------
    *I,MERGL1: Preparing target model ...
    *I,MERGL1: Doing model union ...
    *I,MERGL2: With primary run (mipi_base_test_01/scope/mipi_base_test): mipi_base_test_01/scope/icc_27f588a9_00000000.ucm
    *I,MERGL1: Target model generated successfully.
    *I,MERGL1: Projecting IUS ucd data into the target model ...
    *I,MERGL2: mipi_base_test_01/scope/mipi_base_test:
    *I,MERGL3: Merging instance tree tb to tb:
    *I,MERGL3: Data is projected in to the target model.
    *I,MERGL2: mipi_base_test_02/scope/mipi_base_test:
    *I,MERGL3: Merging instance tree tb to tb:
    *I,MERGL3: Data is projected in to the target model.
    *I,MERGL2: mipi_base_test_03/scope/mipi_base_test:
    *I,MERGL3: Merging instance tree tb to tb:
    *I,MERGL3: Data is projected in to the target model.
    *I,MERGL1: Writing output database cov_work/scope/final:
    *I,MERGL2: Model: cov_work/scope/final/icc_27f588a9_00000000.ucm
    *I,MERGL2: Data : cov_work/scope/final/icc_27f588a9_00000000.ucd
    *I,MERGL1: No Specman coverage databases found in the runs.
    Total conflicts during target model creation: 0
    Total items not merged : 0
    imc>

    So, I'm sure the problem is in your environment somehow. If you'd been pasting the command from an email or documentation, try typing it out manually, in case there are some hidden special characters screwing everything up.

    Please note that 14.10.011 is very old, it came out in early 2014, please consider using a newer version; the last 14.10 update was in May 2016, or you could look at using a supported version such as 15.20.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information