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.

what is the direct definition of primitives at fpga ... ?

Status
Not open for further replies.

segevron

Newbie level 3
Joined
Apr 11, 2012
Messages
4
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
1,310
..........................................
 

Primitives are basic components that makes a FPGA. e.g. Flip-Flips, Lookup-Tables, Shift Registers, and RAMs.
 
To be even clear,Primitives are perhaps vendor specific components such as IO Buffers, clock buffers, multipliers, PLLs, DPLL, BUFGMUX, Etc
You should refer to the datasheet for complete list of primitive components.
 

can u give me a good example for what is not consider as primitive from the elements that the include at the fpga ....?
 

I dont know what you are exactly beating up, but

See, what are all the components that are built-in or embedded in an FPGA is called primitives.
They are PLLs, BUFFERS, DSPMULT, RAM, FIFO, etc. What are all the components that you develop becomes non-primitive and hence you choose your own structural design. for eg, Adder, comparator, BCD, clock divider, etc.

IPs may or may not be a primitive one.....Mostly IPs use primitive components and build their models on top of it.
 

Is primitive components always be same for all devices?.
Also, to simulate, does it require special attention?.
 

Not necessarily. For each devices, the primitive component may change. This is because every new device FPGA will have a newer component, but although for old components, you can use the same old component, but you must make sure to check the "Device name" mentioned in generic parameters. I wonder why even this parameter is required, this information we already provide in project options.

Might be when you wish to make your code portable, this can be used anywhere, just by changing the device name.

To simulate, the simulator tool must be aware of these components functionality. Hence, yes you need to make to tool know where your primitive component lies and what it does. This what we call library compilation. Usually primitive components come as a library(Collection of VHD or V files).
 


Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top