if you're here for the answer to the title, 3:15! Also, I realize the intro focuses on the synchronous always block and memory because that's where I thought I was going when I filmed it and I am following on from my previous video in the series. But actually I cover both, I get into the async pretty quickly at 1:43
A nice job. It might be too advanced for true beginners, but spending time on blocking and non-blocking might make a good video. It’s certainly not required for a beginner, but is good as you advance in your digital logic career.
Yeah I actually originally had an explanation recorded and ended up not including it in the final thing. It was already >10min in total and I figured blocking/nonblocking is a more advanced explanation.
This is very practical and useful , thanks~ By the way, are there any ways or workflows of writing a good and clear verilog testbenches for debugging circuit? Since I couldn't find good videos about testbenches for complex design online.
Excellent video! I have one question. What if I use blocking statements within the synchronous always block? It works fine for me, but is that a bad practice?
Hi, you mentioned that long signals will add up and in that case we should use synchronous always blocks. If the LFSR width was 32 instead of 4 and the case for asserting the led was comparing the lfsr value with a 32 bit constant, would it still be ok to use a combinatorial always block?
It depends on the clock rate and how congested the device is. For 100M and below it's probably fine. The only way to know for sure is to try it on a given design and see.
![[LIVE] : ONE ลุมพินี 96 | คู่เอก "คมอาวุธ vs พันฤทธิ์"](http://i.ytimg.com/vi/ofERaO0gOsE/mqdefault.jpg)
![จากรุ่นใหญ่สุดรวยในเกม FIVEM สู่การติดคุกแก๊งแตกในชีวิตจริง [สรุปแก๊งOREO]](http://i.ytimg.com/vi/Vjj8EX4qpiU/mqdefault.jpg)
if you're here for the answer to the title, 3:15! Also, I realize the intro focuses on the synchronous always block and memory because that's where I thought I was going when I filmed it and I am following on from my previous video in the series. But actually I cover both, I get into the async pretty quickly at 1:43
Yeah ,this is what I wanted you to cover up more upon and please keep making videos 🙏
This is awesome, please keep these videos coming.
Incidentally if you're looking for topics, I think serial transceivers would be great!
Thank you for your tutorial. Asynchronous is really cool!
Really great video, especially, that you focus on practical ways of thinking about the code segments. I hope you keep making videos.
A nice job. It might be too advanced for true beginners, but spending time on blocking and non-blocking might make a good video. It’s certainly not required for a beginner, but is good as you advance in your digital logic career.
Yeah I actually originally had an explanation recorded and ended up not including it in the final thing. It was already >10min in total and I figured blocking/nonblocking is a more advanced explanation.
This is very practical and useful , thanks~ By the way, are there any ways or workflows of writing a good and clear verilog testbenches for debugging circuit? Since I couldn't find good videos about testbenches for complex design online.
LFSRs are very interesting structures with many uses. Eg. GPS codes.
Very cool! I'm very green to verilog/HDLs, but I'll check out your back catalog and maybe finally crack my iCEstick out of its box ^_^
Excellent video!
I have one question. What if I use blocking statements within the synchronous always block? It works fine for me, but is that a bad practice?
Yes it is bad practice. Rather split them into different parts.
Only use = in combinatorial code and assigns.
Hi, you mentioned that long signals will add up and in that case we should use synchronous always blocks. If the LFSR width was 32 instead of 4 and the case for asserting the led was comparing the lfsr value with a 32 bit constant, would it still be ok to use a combinatorial always block?
It depends on the clock rate and how congested the device is. For 100M and below it's probably fine. The only way to know for sure is to try it on a given design and see.
Thank you @@FPGAsforBeginners
nice video, keep up the good work :)
did i missed, or you didnt explained the LOGIC type part. reading about it, but not yet clear.
could you please say couple of words on it? thanks