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.
There is not necessarily anything special about a reset. For example, consider this flip-flop:
process(clk)
begin
if rising_edge(clk) then
if rst_n = '0' then
a_reg <= '0';
else
a_reg <= a;
end if;
end if;
end process;
What if we rename...
To reproduce those graphs exactly as presented, you can do this:
close all; clear all; clc;
% Time to simulate (seconds)
Tsim = 1;
% Sinewave frequency (Hz) and initial phase (radians)
fsine = 4;
phi0 = -pi/4;
% Vector of all sample rates (Hz)
fsamp = [30, 11, 10, 6, 5];
% For each sample...
This thread is not getting any closer to answering my question.
I received a more focused answer to the same question here: link. I will close this thread by summarizing the answer I received there:
Yes... I'm not sure how we got reduced to stating the obvious.
And that doesn't just apply to resets. Everything else in a synchronous system is synchronous for a very good reason. This isn't some agenda.
In the special case of a reset, in some cases, it is worth investing extra effort to deal...
I would like to finally close this thread by sharing a superb response I received on the Xilinx forums from a user named "markg@prosensing": link.
I would encourage anyone interested to read and re-read his whole response because it is incredibly comprehensive. He finishes with this concise...
The diagram you showed looks in many ways extremely similar to Xilinx. If "LAB Wide" means "Slice Wide", then control signals are shared, just like in Xilinx slices.
Therefore, similar to Xilinx, I think a synchronous reset could be implemented in 2 ways: using SCLEAR, or by including the...
I don't think this is correct. The latest Intel "Design Practices" recommend the use of a standard asynchronous assert, synchronous de-assert reset. See this link:
Intel call this "synchronized asynchronous reset". I call it "asynchronous reset" (but not "fully asynchronous reset", which is...
I have worked on several projects with Intel/Altera FPGAs, but I must admit I don't know them so well. Therefore, I won't comment as I don't want to spread incorrect information.
One of the articles by Ken Chapman that I linked above is titled "Get your Priorities Right – Make your Design Up to...
The distinction typically applies to 3 things:
The assertion of the reset signal.
The de-assertion of the reset signal.
The FF circuit.
1660559062
The usual solution to this is to plan a proper resetting strategy. In a modern FPGA, the general guidelines are:
Only reset flip-flops that...
I specifically asked in my original post if the nature of the reset has an impact.
In my experience, a fully asynchronous reset is absolutely never used in a synchronous system. If a reset synchronizer is used to synchronize de-assert, then (in the majority of my experience) this is still...
No, I didn't mix anything up. My question is nothing to do with reset synchronization.
I'm asking about a 2 flip-flop synchronizer and whether there is any potential drawback to resetting those registers (whether you think there may be a reason to do that or not).
Is there some problem/drawback with resetting a 2 flip-flop synchronizer?
Is the answer the same for both synchronous and asynchronous (i.e. asynchronous assert, synchronous de-assert) resets?
The reason to add a reset would be so that the flip-flops can be either set or cleared when a reset signal is applied.
I can think of plenty of cases where this would not be necessary, and some where it would. For one example, what if the destination clock is not running? An async reset would...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
