Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

doubt in VHDL.....?uregent..

Status
Not open for further replies.
W

walkman

Member level 1
Joined
Jul 24, 2010
Messages
40
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,286
Location
hyderabac
Activity points
1,532
subtype UREAL is REAL;
type UREAL_VECTOR is array (natural range <>) of UREAL;
type UREAL_TABLE is array (natural range <> , natural range <>) of REAL;
function resolved (S : UREAL_VECTOR) return UREAL;
subtype RREAL is resolved UREAL;



could you plz any one explain the above lines..i understood first line .but in second line what is meaning of "natural range<>".and i didn't understood 4,5 lines
 

Someone like silly code.

the first line is one of the most redundant bits of code I have ever seen. why do you make a subtype of real without setting a range you might as well just leave it at real.

the natural range bit is telling users that the range of this vector, when declared, must be anything from 0 to integer'high. So

signal a: ureal_vector(0 to 10); --valid
signal b: ureal_vector(99 downto 66); --valid
signal c: ureal_vector(-1 to 1); --invalid as -1 is not in the natural range.

But then finally someone is resolving the real type. Is this for some model, maybe of an analogue circuit? this code is not synthesisable.
 

Thanks for your reply.. yes it is code for analog modeling not for design just for simulations
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top