Search Engine www.edaboard.com

39 Threads found on edaboard.com: Fast Path
Hi All I need to add a 21-bit signal to a 32-bit signal, and it won't generate carry bit. Since the clock is really fast, I'm trying to figure out how complex the ADDER logic might be, based on standard library from TSMC. For example, will the critical path have more than 21 NAND-like level of combo cells? Can some body shed lights on ho
How are you fixing setup violations? If you are shortening data path to meet setup check, I don't see why that will produce new set up violations. If the data travels fast, then fixing setup may produce hold violations .
Any attempt to change the current flowing through an inductor sets up a counter-emf which opposes and slows down the change. The opposition is called the reactance (X). The faster the change, the higher the reactance: For a sine wave, X = 2pifL. Hence a fast-changing signal passes more easily though a path of low inductance than through one (...)
Yes, both setup & hold violations are possible in the same path. Setup analysis will be done in the slow corner, where as Hold is done in the fast corner. Now, look at this way, the combo path consists of only HVT cells ( which usually gives more delay in slow corner, less delay in fast corner ). This is due to delay (...)
The DC current that can flow in the substrate should be very small. However, a noticeable amount of current can flow through the substrate during transitions specially if you have any fast switching signals and having low resistance path can create large voltage drops. It is good to directly connect the vsub in a star connection to avoid debiasing,
The clock gating hold violation is usually because: the clk_gate_enb reach the gating cell too fast than the clock signal. So, of cause you can add buffer on the clk_gate_enb path to eliminate the hold violation. (Assume the clk_gate_enb and clock signal are SYNC to each other)
Hai ramesh you can set multicycle path for both the conditions i.e from slow clock to fast clock and from fast clock to slow clock for the condition from slow clock to fast clock set_multicycle_path x -setup -from launch_clk(slow) -to capture_clock(fast) -end ---> which will add (...)
1N4001 diode is far to slow. Use 1N4148 or similar fast switching diode .... :wink: IanP
So you need to refer to the other options. Shunt measurement will probably require a fast differential amplifier to pick up the voltage. Current transformer can be easily made: A small, high ?r ferrite torroid of 5 to 10 mm diameter. 10 to 50 turns secondary winding, terminated with a low ohmic resistor or 50 ohm oscilloscope input.
Hi, I am searching for a fast method to find total number of paths in a circuit during synthesis. I am using design compiler and until now the only solution that I have is to write all paths in a file using following command report_timing -nworst HUGE_NUMBER > file.txt and then use a "grep slack file.txt | wc -l" to extract the (...)
Excuse me for bad writing. I'm poor in English language. Is there anyone who is in this field of study? I am study at the Quantum Dot solar cell, in past two months. but I can't find the path to learn it. I need to learn it fast. because I have thesis, and should do it in 9 months. I need help, to know how can I learn it. if I read paper , Ho
Asynchronous Sequential circuits do not use a clock and can change their output state as fast as the signal path's propagation delay from the input allows. This means they can be faster than Synchronous Sequential circuits. However, they are considerably more likely to suffer from race conditions (inputs arriving at different times causing (...)
Hi all !! what is CRPR? I have a basic doubt of why CRPR is is a problem in On Chip variation (OCV) where we take two different corners (i,e fast and slow path delays) actually this can be a true scenario right?? why do we need to remove it? and what do they mean by reconvergence Pls clr my doubts Thanks in advance
What exactly do you mean by a combinatorial loop? quartus has no problem with this : a_temp <= b_temp or a; b_temp <= not a_temp; b <= b_temp; If by 'no problem' you mean that Quartus generates warnings that you ignored, then yes, there is 'no problem'. Here is what Quartus has to say... Warning: Found combinati
In OCV (On Chip Variation), we assume things can be very different within the chip, under single operating condition. So to simulate the most pessimistic case for: - setup: assume data launch path is really slow & data capture path is really fast. - hold: assume data launch path is really fast & data (...)
Well, depends on where most of your critical fast switching signals are routed. If it's TOP, then a TOP-VCC-GND-BOT will have a longer return path for these signals. Otherwise if this is not a very high-speed (fast switching) PCB, then ideally nothing should change..
The main intention for checking hold time is to make sure that the previous data is not over written. So if min path data arrives to fast just after the clock then u will get hold timing violations. u have to fix these by adding delay buffers, so that ur min path is delayed. Hope it clears ur doubt.
Be careful with zenner diodes ; the switching may be too slow. ; the damage might be done already. Use transorbs and or MOVs that will switch on fast.
I have a similar test to complete, however my pulses are approx. 300 ps wide. I thought about using a fast comparator, but it is still a long way for me, untill I'll be able to test this circuit. The comparator I was intending to use is the following: Analog Devices ADCMP572 It has a 8 GHz equivalent input raise time bandwidth (80ps min puls
fast slews make paths faster slow slews makes paths slower in your datapath ... fast slews hurt hold and help setup. it's the opposite for slow slews in your clock path it all depends on what type of skews the different slews are causing