• 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. $fmonitor

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 64
  • Views 15945
  • 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

$fmonitor

archive
archive over 17 years ago

Hi everyone,
I am trying to monitor the signals within my testbench into a file but it always gives me the following warning
** Warning: No matching channel descriptor '2' found.  Ignoring the write in to the invalid channel.
#    Time: 0 ns  Iteration: 2  Instance: /textgenerator

here is an example:

module textgenerator;
    integer fd;
    logic clk;
   
initial begin
        clk
        #2 clk=!clk;
    end
    
initial begin 
  
fd=$fopen("file.txt");
$fmonitor(fd,"clk:%b",clk);
$fclose(fd);
        end
endmodule


could someone please help me on how to save the monitored signals within a file


Originally posted in cdnusers.org by ROOZ
  • Cancel
  • archive
    archive over 17 years ago

    Try deleting the $fclose line.

    Shalom.Bresticker@intel.com


    Originally posted in cdnusers.org by shalom
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    thx for quick reply but it doesn't seem to help....


    Originally posted in cdnusers.org by ROOZ
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    my bad...you are right. it work if i delet it. thanks alot for your quick response


    Originally posted in cdnusers.org by ROOZ
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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