VCS error message - Error-[SFCOR] Source file cannot be open

[lokesh garg]

VCS error message

i made a verilog code for counter. for simulation i went to my working directory i run my my code following error is coming...

Error-[SFCOR] Source file cannot be opened for reading
Source file "module" cannot be opened for reading.
plzz help me

 

[haneet]

Re: VCS error message

i think probably your verilog code is missing the module/endmodule

regards,

haneet

 

[divya763]

Re: VCS error message - Error-[SFCOR] Source file cannot be

Hi Vijay,

I am working on VCS now and getting the same error as you. Could you help me, if you have figured out how to rectify the problem.

Thanks
Divya

 

[nsingh95]

Re: VCS error message - Error-[SFCOR] Source file cannot be

Hi Vijay,

I am working on VCS now and getting the same error as you. Could you help me, if you have figured out how to rectify the problem.

Thanks
Divya

Hi ,
This error generally comes when the simulation tool ie vcs does not find the module in the working directory.So, fisrt check whether have you compiled it properly or not.2nd you check whether in the run command ,bsub -Ip -q .... (whatever) ,you are mentioning the module name only.Just check and I think it will work out . Also check the access information of the file it should be r-x r-x r-x.

 

[vidarson_qin]

Probably, if you copy your files from dos system to unix system, this error will be printed. Use dos2unix on your files to fix this error.

 

[cvc]

Re: VCS error message

i made a verilog code for counter. for simulation i went to my working directory i run my my code following error is coming...

Error-[SFCOR] Source file cannot be opened for reading
Source file "module" cannot be opened for reading.
plzz help me

Show us how you invoke VCS. My guess is you had "file.sv" as

module m;
endmodule : m

And then you passed to VCS (wrongly) with -f arg as:

vcs -f file.sv

If the above guess is right, remove the -f, it should work. Else show us your exact command for more help.

Regards
TeamCVC
www.cvcblr.com/blog