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.

Recent content by stanford

  1. S

    arbiter - flopping the grant signals

    Anyone familiar with arbiter design know how we can deal with flopped grant and what we typically do to avoid this problem?
  2. S

    arbiter - flopping the grant signals

    Here is a figure to help. If we flop the grant, we would get 2 grants if we try to request only 1, because the requester would drop the req once it sees the flopped grant.
  3. S

    arbiter - flopping the grant signals

    Sorry, i didnt know how to better explain without drawing the waveform. Typically, gnt signals are not flopped for this reason. if it is, you will end up with an extra grant on the last request, because the slave will keep req up until it sees grant. So for example, if slave wants to make 1...
  4. S

    arbiter - flopping the grant signals

    No, there is an issue. The slave will drop its req after the grant, which is delayed by 1 cycle. So the arbiter will grant 1 extra request. You can draw out the waveform if you don't see it intuitively.
  5. S

    arbiter - flopping the grant signals

    due to timing, if we need the arbiter to flop all its output, how can we make it work? If we don't do anything, we could get 'extra' grants.
  6. S

    min skew check

    Why do you want delay_clk > delay_data in Source-Synchronous path? Wouldn't this make the hold violation worse?
  7. S

    min skew check

    ah thanks, any other reasons?
  8. S

    min skew check

    Why do we have a check for min skew? What does this help avoid? Thanks!
  9. S

    source synchronous bus and hold violation

    When we send data and clk using source synchronous fashion, and if we assume that skew is ~0, the receiver could have setup and hold violations right? Why are we more concerned about hold violations with source synchronous bus? Isn't setup violation just as probable as hold violation?
  10. S

    Reset Value using a parameter

    I am using systemverilog, and it does not work. Syntax is not correct. Does anyone know how to fix it?
  11. S

    Reset Value using a parameter

    Let's say that I have a data[WIDTH-1:0]. I want to use a parameter in RTL to provide the reset value for this data. parameter RESET_VALUE = 5; logic [WIDTH-1:0] data; always_ff @(posedge clk) if (~reset) data <= WIDTH'd (RESET_VALUE); else .... How do I make this work syntax...
  12. S

    Using generate and for loop to index signal name

    Say I have inputs as follows: input in0; input in1; input in2; input in3; ... and what I want to do in generate for loop is something like this. b[0] = in0; b[1] = in1; b[2] = in2; ... and so on. The problem is I cant index the inputs using the variable 'i' in the generate for loop. How can...
  13. S

    default statement in case

    If i put this statement (state_nxt = state;) at the very top of the always_comb, the default statement in 'case' is not required for it to not synthesize into a latch. Is this correct? Would you still put the default statement for simulation purposes and why? always_comb begin state_nxt =...
  14. S

    Beginning and end of a time step

    I understand the theory, but I just wanted to make sure my understanding of the real life example makes sense. If someone has a good understanding of this topic, could you please confirm or correct it? thanks
  15. S

    Beginning and end of a time step

    Can you take a look at my steps above? I think you are saying the same thing.

Part and Inventory Search

Back
Top