• 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. Custom IC SKILL
  3. Re: prevent string choices of verilogA from splitting into...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 9919
  • 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

Re: prevent string choices of verilogA from splitting into two lines

slim15
slim15 over 3 years ago

Hi,

I created a verilogA block to generate different static output depending on a parameter call Mode that can have two values, "power down" and "calibration". This verilogA is instantiated on a schematic view and the chosen values is determined by a pull down menu by modifying the CDF of this block where Mode is set as a cyclic button and choices having the following entry: power down,calibration

The verilogA code is as follow:

// VerilogA for sandbox, simCell_DAC, veriloga

`include "constants.vams"
`include "disciplines.vams"

module simCell_DAC (VDD, VSS, DAC_D);

output [1:0] DAC_D;
inout VDD, VSS;

electrical [1:0] DAC_D;
electrical VDD, VSS;

integer VAL_DAC_D=0;


parameter string Mode = "power down";

genvar i;

analog begin

case (Mode)
"power down" : VAL_DAC_D = 1;
"calibration" : VAL_DAC_D = 3;
default: VAL_DAC_D = 2;
endcase

for (i=1; i>=0; i=i-1) begin
V(DAC_D[i],VSS) <+ (VAL_DAC_D>>i)&1 ? V(VDD) : V(VSS);
end

end

endmodule

On the occasion where the netlister splits the "power down" into two lines like below

  I0 (VDD_TOP VSS_TOP DOUT\<1>\ DOUT\<0\>) simCell_DAC Mode="power \

down"

the default option within the case-statement will be called instead of the "power down". Is there a way to either prevent the netlister from splitting the "power down" string into two lines or verilogA case statement to accept breakage?

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 3 years ago

    I don't see this behaviour unless I mess around with hnlMaxLineLength. So try setting this (best in the .simrc, but could also be in .cdsinit I think):

    hnlMaxLineLength=1024

    (you might also need to set hnlSoftLineLength=0 )

    Please contact customer support though - the netlister should behave properly here, especially if it affects the parameter passed into the Verilog-A module.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 3 years ago

    I don't see this behaviour unless I mess around with hnlMaxLineLength. So try setting this (best in the .simrc, but could also be in .cdsinit I think):

    hnlMaxLineLength=1024

    (you might also need to set hnlSoftLineLength=0 )

    Please contact customer support though - the netlister should behave properly here, especially if it affects the parameter passed into the Verilog-A module.

    Andrew

    • 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