Results 1 to 6 of 6

Thread: problems about hdl parser

  1. #1
    Join Date
    Sep 2005
    Posts
    20

    problems about hdl parser

    hi,
    when i do mixed signal simulation in cadence, some problems occured.
    i have compiled some digital .v files using verilog-xl 05.40.003-s, and it finished without errors.
    and when i build a block in config and with the same code, the HDL parser give some errors at such codes as "wire signed", "20'sh00004" and "always @(*)",

    so can anyone tell me what to do ?
    thanks

  2. #2
    Andrew Beckett Guest
    On Mon, 28 Nov 2005 19:10:08 -0600, dennishgj@yahoo-dot-com.no-spam.invalid
    (arsenal) wrote:

    hi,
    when i do mixed signal simulation in cadence, some problems occured.
    i have compiled some digital .v files using verilog-xl 05.40.003-s,
    and it finished without errors.
    and when i build a block in config and with the same code, the HDL
    parser give some errors at such codes as "wire signed", "20'sh00004"
    and "always @(*)",

    so can anyone tell me what to do ?
    thanks
    You've not provided enough information for anyone to realistically be able to
    help.

    Andrew.

  3. #3
    Join Date
    Sep 2005
    Posts
    20
    thanks andrew,
    i have written some codes in verilog and it passed compilation and can be synthesized, and the following statements are included,
    wire signed [33:0] mydata;
    assign mydata=34'h3f0000000;
    assign mytest=(mydata == -34'sh010000000);
    ...

    however,when i use the same codes in the behavioral view of a cell, which will be recompiled by HDL parser, errors were given in the above statements and marked as "syntax error", it seems HDL parser uses another version of verilog-xl and doesnt accept the syntax as "signed","sh"...

    thanks a lot and urgent for your help.

    arsenal

  4. #4
    Andrew Beckett Guest
    On Tue, 29 Nov 2005 15:10:10 -0600, dennishgj@yahoo-dot-com.no-spam.invalid
    (arsenal) wrote:

    thanks andrew,
    i have written some codes in verilog and it passed compilation and can
    be synthesized, and the following statements are included,
    wire signed [33:0] mydata;
    assign mydata=34'h3f0000000;
    assign mytest=(mydata == -34'sh010000000);
    ..

    however,when i use the same codes in the behavioral view of a cell,
    which will be recompiled by HDL parser, errors were given in the
    above statements and marked as "syntax error", it seems HDL parser
    uses another version of verilog-xl and doesnt accept the syntax as
    "signed","sh"...

    thanks a lot and urgent for your help.

    arsenal
    Ah, that's due to "van" being used to analyse the code. This is an old tool
    which doesn't understand Verilog 2001 stuff.

    If you set the following variable in your .cdsinit or in the CIW:

    schHdlUseNcvlogForVerilog = t

    Then it will use ncvlog instead (of course, you need to have ncvlog in the
    path).

    This is described in solution 11192234 on Sourcelink.

    Regards,

    Andrew.

  5. #5
    Join Date
    Sep 2005
    Posts
    20
    thank you very much Andrew,

    i have done as you told me and now there is such a warning as:
    ncvlog: *W,DLNOHV: Unable to find an 'hdl.var' file to load in.
    will this warning matter?

    and in my code, i includes more modules in one file, like following:

    module a;
    b #(3) b0(..);
    b #(4) b1(..);
    ....
    endmodule

    module b;
    parameter PB=1;
    ...
    endmodule

    and HDL parser just creates only one cell of b, and can it distinguish the different parameters?


    thanks

    arsenal

  6. #6
    Andrew Beckett Guest
    On Wed, 30 Nov 2005 15:10:15 -0600, dennishgj@yahoo-dot-com.no-spam.invalid
    (arsenal) wrote:

    thank you very much Andrew,

    i have done as you told me and now there is such a warning as:
    ncvlog: *W,DLNOHV: Unable to find an 'hdl.var' file to load in.

    and when i exit the hdl parser, it doesn't prompt me to create a
    symbol for the cell.

    thanks

    arsenal
    Haven't got time to check this now, but try creating an hdl.var file in the
    working directory with the following contents:

    SOFTINCLUDE $IUSHOME/tools/inca/files/hdl.var

    where $IUSHOME is set to wherever your IUS installation is (can be whatever
    env var you like, of course).

    Andrew.

Similar Threads

  1. Drawings...how many problems!!!!
    By LouR in forum Pro/Engineer
    Replies: 0
    Last Post: 02-16-2005, 09:33 AM
  2. LSP to SCR problems
    By MJB in forum Customization
    Replies: 1
    Last Post: 02-04-2005, 02:19 PM
  3. Problems with DXF's
    By Mike07 in forum AutoCAD
    Replies: 1
    Last Post: 12-16-2004, 03:11 AM
  4. X-REF PROBLEMS
    By WOLFRUTHER in forum AutoCAD
    Replies: 2
    Last Post: 09-22-2004, 01:21 PM
  5. IPC problems
    By Henrik Johansson in forum Cadence
    Replies: 3
    Last Post: 09-04-2004, 10:43 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other forums: Access Forum - Microsoft Office Forum - Exchange Server Forum