Search Engine www.edaboard.com

Primitives

Add Question

139 Threads found on edaboard.com: Primitives
I'm assuming you are talking about a Verilog description. Strengths of the inputs do not affect the strength of the output of logic primitives gates. Only the MOS and tran primitives pass strength.
You didn't supply enough of the code to allow someone to answer. If you are using the DDR controller from Xilinx then the I/O primitives are already inside the controller code. You can't add some multiplexers outside the DDR IP core without getting errors just like you are getting. What you would be doing is adding logic between the I/O primitive (
For fundamental primitives such PLLs (or anything of this soft) definitely not. On the other hand - there may be some 3rd party Xilinx/Altera certified cores that do require per device royalties.
Not sure what you want to do. This is something else other than propagation delays. Xilinx FPGAs provide adjustable IDELAY and ODELAY primitives in the device's I/O blocks. They are most often used to make small adjustments to I/O timing, but with some imagination you can find other creative uses. It's a bunch of delay taps that you can adjust on
output node comes first in primitives Even if this is the case for certain libraries, you shouldn't rely on it. There's no general language rule suggesting a specific order. I think, if you use lazy ordered parameter assignment instead of unequivocal named assignment, you deserve the trouble.
Circuit design is much more than schematic capture and simulation. LTSpice will not be much help in layout verification, post-routing simulation or any of the stuff that you need when it "gets real". For many device models in LTSpice the primitives lack some of the geometry fields you would want to see in IC design where this is a (perhaps, the) cr
Schematic to layout (given a suitably constructed primitives library) is offered (some assembly required). Code to layout, I have never seen in the analog realm. Structural verilog / veriloga (where every element at the lowest level is a real component, transistor / resistor / capacitor, call and no "loop" or such constructs, might be massaged int
Check if for some reason you drew these primitives in another layer, not the silk.
It's self explanatory the blocks are not Spartan6 primitives. You are compiling a design meant for a different device type and the primitives don't exist in Spartan6. Looks like it might be for a Virtex or Kintex 7
An enable. always @(posedge clk) begin if (enable) .... end That is not "clock gating". e.g. Xilinx has BUFGCTRL, BUFGMUX, BUFGMUX_1, and BUFGMUX_CTRL primitives for clock multiplexing. I suppose if you are a masochistic you can "gate" the clock with a LUT feeding the clock input or a LU
In whatever form, I would just port it for the current FPGA and then try simulating it. There might be more problems in synth the design. I guess the Xilinx primitives/libraries used would be the main bone of contention. But it is definitely possible to change them after they have been identified.
Although being unnusual to add a component at the library not at the top layer, I presume that you could do that just by drawing this component with the bottom primitives ( Pads, Silkscreen, etc... ).
You need to scroll back further and address any complaints about libraries not found, failure of extract process, etc. I see some complaints about not being able to find what look like basic PDK library primitives, maybe your library setup is not making it to the verification tool's setup or something like that. Technology file needs attached to
Hi, I design protocol, but when i implementing the design using ZYBO board. i have used constraint file, but i get Error when translating the design, Error is: ERROR:NgdBuild:924 - input pad net 'clk' is driving non-buffer primitives:
You can draw the contour of the antenna on any mechanical layer end convert it to solid region: 1) draw the contour on mechanical1 layer for instance 2) select the contour 3) go to Tools>Convert>Create Region from Selected primitives 4) click right button on the region and select Properties 5) change the machanical1 layer to TOP layer
I think this is best done in veriloga (which Spectre digests just fine, and Cadence supports editing and view-switching). You will want to error-trap that denominator, and a poly- source / analogLib primitives kludge probably doesn't have much for that. I'd recommend to find a resistor veriloga model, off the Web, and just mess with the guts.
You don't need to use low level primitives to implement BLVDS. For Cyclone III, it's sufficient to assign the BLVDS IO standard for the respective inout pin and connect the inout signal as you d with other biderectional signals. With other devices like Cyclone V that don't provide a BLVDS standard, you'll use Differential SSTL instead. The quote
If these models are not from that foundry*flow then they ought to use the analogLib primitives and you specify the model path to suit yourself. TSMC surely doesn't want to know about your provate models.
Without constraints that directs the synthesis tool to keep redundant logic cells, or using low level primitives to describe the circuit, you won't get a working ring oscillator. I could tell you how to do it in Altera Quartus, I'm not using Xilinx. But I'm quite sure that it's possible with Xilinx tools, most likely you'll find respective hints
I'm sort of at a loss as to what your real question is. I'm not sure if you are confusing yourself with structural coding v.s. behavioral coding styles. A synthesis tool uses a library of vendor primitives and maps the HDL to those primitives. If you specify an AND/OR/XOR etc gate in your HDL, then the synthesis tool looks for a gate that does t