Stats

  • Locked Locked
  • Replies 6
  • Subscribers 66
  • Views 18414
  • 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

SV DPI: veriusertfs

archive

Hi,

I'm trying to compile C file that contain the following:

#include
#include
#include
#include "veriuser.h"
#include "acc_user.h"
....
....

s_tfcell veriusertfs[] = {
//{userfunction, 0, 0, fio_size32, myfclose, 0, "$myfclose"},
{usertask, 0, 0, 0, myfopen, 0, "$myfopen"},
{usertask, 0, 0, 0, myfclose, 0, "$myfclose"},
...
...
{0} //
};

the problem is that the compiler (gcc c-file.c -c -I /include -o c-file.o) didn't recognize s_tfcell veriusertfs[], I have get the following message:

//372: parse error before "veriusertfs"
//374: warning: braces around scalar initializer
//374: warning: (near initialization for `veriusertfs[0]')
//374: `usertask' undeclared here (not in a function)
//374: initializer element is not constant
//374: (near initialization for `veriusertfs[0]')
//374: warning: excess elements in scalar initializer
//374: warning: (near initialization for `veriusertfs[0]')
//374: warning: excess elements in scalar initializer
...
...

All the include files are exist, what I'm missing?? are the include files too old??

Thanks, Benni.


Originally posted in cdnusers.org by bennik
Parents

  • sorry, "myopen(...)" is task and I changed the import accordingly but it still not work

    import "DPI-C" context task myfopen(input string "./script.txt", output FILE fp);
    |
    ncvlog: *E,EXPIDN (../monitor/mon_top.sv,48|65): expecting an identifier [3.2][3.8][3.9(IEEE)].
    import "DPI-C" context task myfopen(input string "./script.txt", output FILE fp);
    |
    ncvlog: *E,EXP1RD (../monitor/mon_top.sv,48|73): expecting at least one register variable [3.2.2(IEEE)].
    import "DPI-C" context task myfopen(input string "./script.txt", output FILE fp);
    |
    ncvlog: *E,SVNOTY (../monitor/mon_top.sv,48|78): Syntactically this identifier appears to begin a datatype but it does not refer to a visible datatype in the current scope.
    import "DPI-C" context task myfopen(input string "./script.txt", output FILE fp);
    |
    ncvlog: *E,EXPCORP (../monitor/mon_top.sv,48|81): Expecting a ',' or ')' [A.1.4(IEEE-2001)].
    import "DPI-C" context task myfopen(input string "./script.txt", output FILE fp);
    |
    ncvlog: *E,EXPRPA (../monitor/mon_top.sv,48|81): expecting a right parenthesis (')') [A.2.6(IEEE)].
    import "DPI-C" context task myfopen(input string "./script.txt", output FILE fp);
    |
    ncvlog: *E,EXPENM (../monitor/mon_top.sv,48|82): expecting the keyword 'endmodule' [12.1(IEEE)].


    Originally posted in cdnusers.org by bennik
Reply

  • sorry, "myopen(...)" is task and I changed the import accordingly but it still not work

    import "DPI-C" context task myfopen(input string "./script.txt", output FILE fp);
    |
    ncvlog: *E,EXPIDN (../monitor/mon_top.sv,48|65): expecting an identifier [3.2][3.8][3.9(IEEE)].
    import "DPI-C" context task myfopen(input string "./script.txt", output FILE fp);
    |
    ncvlog: *E,EXP1RD (../monitor/mon_top.sv,48|73): expecting at least one register variable [3.2.2(IEEE)].
    import "DPI-C" context task myfopen(input string "./script.txt", output FILE fp);
    |
    ncvlog: *E,SVNOTY (../monitor/mon_top.sv,48|78): Syntactically this identifier appears to begin a datatype but it does not refer to a visible datatype in the current scope.
    import "DPI-C" context task myfopen(input string "./script.txt", output FILE fp);
    |
    ncvlog: *E,EXPCORP (../monitor/mon_top.sv,48|81): Expecting a ',' or ')' [A.1.4(IEEE-2001)].
    import "DPI-C" context task myfopen(input string "./script.txt", output FILE fp);
    |
    ncvlog: *E,EXPRPA (../monitor/mon_top.sv,48|81): expecting a right parenthesis (')') [A.2.6(IEEE)].
    import "DPI-C" context task myfopen(input string "./script.txt", output FILE fp);
    |
    ncvlog: *E,EXPENM (../monitor/mon_top.sv,48|82): expecting the keyword 'endmodule' [12.1(IEEE)].


    Originally posted in cdnusers.org by bennik
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.