Single Entity - Multiple architectures

Guest #3519024
Rate this post
• ▲ useful
▼ not useful
I am a beginner in VHDL, I have a very basic question regarding Single 
Entity having multiple architectures. For example when the VHDL code is 
compiled (a single file containing one entity and 3 architectures), how 
does the compiler will decide which is the default architecture; or 
there isn't anything like Default Architecture.

I will be really grateful to any help from experts here.
Thanks in advance.
Guest #3519220
Rate this post
• ▲ useful
▼ not useful
In the VHDL standard this is defined in the chapter on "default Binding 
Indication". VHDL differentiates between Primary design units (Entity, 
Package Header, Configuration) and Secondary design units (architecture 
body, package body).

You must compile (well, analyse in the VHDL terminology) a primary 
design unit first. Sort of logical if you think about it, except perhaps 
for configurations. Configurations only become 'real' at elaboration 
time, i.e. after you have analysed everything into a library and are 
building your model, starting your simulation or whatever.

If you compile multiple secondary units and don't specify a binding 
(e.g. link a specific architecture to a specific entity) then the 
default binding is the "most recently analysed" architecture .... the 
last one analysed.

Charles

Reply

Note: the original post is older than 6 months. Please don't ask any new questions in this thread, but start a new one.

Formatting
  • [c]C-Code[/c]
  • [vhdl]VHDL-Code[/vhdl]
  • [code]code in other languages, ASCII drawings[/code]
  • [math]formula (LaTeX syntax)[/math]
  • [[Title]] – link to an article
  • Link to another post: right-click its post ID (#8078628), copy the address, paste it into the text

More about formatting

Post long source code as an attachment, not in the text.

Already registered? Log in

Not shown to anyone. We send you a link; your post appears once you confirm it there.

By submitting you create a free account and accept the terms of use.