A digital UDP can be combinational or sequential. In a combinational UDP, the output is a wire type. In a sequential UDP, the output must be declared as type reg. In the V-AMS BNF, the discipline_identifier appears on UDP reg declarations. Also, in the V-AMS BNF, in udp_output_declaration, the discipline_identifier appears before the reg keyword, whereas in the udp_reg_declaration BNF, the disicipline_identifier appears after the reg keyword. That seems inconsistent. Shalom > -----Original Message----- > From: owner-verilog-ams@server.eda.org > [mailto:owner-verilog-ams@server.eda.org] On Behalf Of David Miller > Sent: Tuesday, August 11, 2009 4:26 PM > To: Verilog-AMS LRM Committee > Subject: Re: UDP net with discipline identifier > > Well the only discipline_identifier that would make sense > would be the discrete > - dlogic or wire. > > I don't know enough about digital, but if it doesn't make > sense to have a UDP > output declared as dlogic or wire then I guess it should be removed. > > However, the inclusion of the discipline_identifier is the > only deviation we > made from 1364. > Perhaps Graham may have more info on why we made this addition? > > Regards > Dave > > > Surya Pratik Saha wrote: > > Hi, > > I have seen following rule in Verilog AMS 2.3.1: > > *udp_output_declaration ::= > > { attribute_instance } output port_identifier > > | { attribute_instance } output [ discipline_identifier ] reg > > port_identifier [ = constant_expression ] > > udp_input_declaration ::= { attribute_instance } input > > list_of_port_identifiers > > udp_reg_declaration ::= { attribute_instance } reg [ > > discipline_identifier ] variable_identifier > > * > > But I think there is no meaning to add discipline > identifier with udp > > nets. So LRM needs a correction here. Please let me know if > I am wrong > > here, otherwise I will file a Mantis. > > > > -- > > Regards > > Surya --------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Aug 13 06:49:31 2009
This archive was generated by hypermail 2.1.8 : Thu Aug 13 2009 - 06:49:51 PDT