Get the job!

I hate multicycle paths. They have their uses, but they are not simulatable. When you declare something: set_multicycle_path -setup -from a_in -to c_out 2 set_multicycle_path -hold -from a_in -to c_out 1 You are essentially telling the tool that it has one extra clock cycle (a total of 2 clocks) to …

Hopefully you’be gotten most of the clock crossing questions. If you missed them all or if you weren’t able to at least work through them with some help, then it’s very doubtful I’ll be giving a thumbs up. As I have mentioned in replies to comments, they are so essential …

The next question is more general. Just basically to get an idea if you know the parts of a FIFO and how they work together. I would recommend reading Cliff Cummings paper on the subject: http://www.sunburst-design.com/papers/CummingsSNUG2002SJ_FIFO1.pdf This is a short post, since Cliff covered this very thoroughly and there is …

We’ve been through a simple synchronizer and constraints. Now we need to move data from one clock domain to another. There are a couple of ways to do this, but one thing I am hoping to see is efficiency. So you might be thinking FIFO, but try to think of …

So I’ve asked a question and hopefully you made it through it, possibly with a little help. Now, depending on experience, I’ll ask if you’ve worked in either Quartus or Vivado to develop constraints for the circuits. This helps fill me in how much of the flow you’ve worked on. …