{"id":371521,"date":"2024-05-21T04:50:42","date_gmt":"2024-05-21T04:50:42","guid":{"rendered":"http:\/\/savepearlharbor.com\/?p=371521"},"modified":"-0001-11-30T00:00:00","modified_gmt":"2024-05-21T04:50:42","slug":"","status":"publish","type":"post","link":"https:\/\/savepearlharbor.com\/?p=371521","title":{"rendered":"The results of 7 Verilog meetups + the goals and the steps going forward<\/span>"},"content":{"rendered":"
<\/div>\n
\n
\n
\n
\n
<\/figure>\n

Since the New Year we had 7 Verilog meetups<\/a> at HackerDojo<\/a>. We discussed the modern way of designing digital circuits using hardware description languages, the exercises on FPGA boards and the topic of microarchitecture. For the last two sessions we went over the most basic CPU core that can be used as a baseline for further exercises.<\/p>\n

There are video recordings available for some meetups and Zoom calls<\/a>. Particularly I recommend to see the first<\/a> video (it gives a general overview) and a video about a baseline CPU core <\/a>we can use for a number of exercises.<\/p>\n

From the beginning we planned to split the meetups into two types of sessions:<\/strong><\/p>\n

1.Regular meetings of a small R&D team that develops multiple open-source repositories of SystemVerilog examples. Two focuses: compatibility (boards, ASIC and FPGA toolchains, peripherals) and microarchitecture (what the electronic companies ask you during a job interview — pipelines, FIFO queues, arbiters etc).<\/p>\n

2) Occasional Show-and-Tell sessions for a wider audience interested in reconfigurable hardware as a way of computing different from software. Displaying graphics and recognizing music using FPGA boards, together with some presentations from the members of the regular R&D meetings: How do FPGAs work? What is their role in the electronic industry? How is it related to mass-market electronic devices? Can you make your own ASIC (Tiny Tapeout, OpenLane, eFabless etc)?<\/p>\n

During the meetups there were three kinds of participants:<\/strong><\/p>\n

1) People who are curious about the technology but not interested in doing exercises. This is the prime audience for show-and-tell sessions.<\/p>\n

2) People who are interested in learning new things to get additional career options. They can take some projects, but they may not be interested in coming every Sunday. Many prefer to work at home and communicate via email or Zoom.<\/p>\n

3) People who already work in the field (like CPU designers) who can be interested in more advanced material (like new branch predictors or design verification techniques for multithreading), but who get bored when the discussion moves around basic topics or discussions about the example infrastructure (pins, toolchain details).<\/p>\n

On the necessity of doing exercises<\/strong><\/p>\n

At this moment, in order to make progress toward both goals (implementing new examples and show-and-tell sessions) it is essential for the regular participants (mostly from group 2) to solve all the homework exercises (see the list here) in parallel with studying the recommended materials. I can review the results over the internet and during Zoom sessions.<\/p>\n

There is no other way. I can spend a year talking, but if a listener does not do the exercises, there is no progress. In fact it happens all the time with recent college graduates: a graduate may have in his resume some sophisticated microarchitectural things (Tomasulo algorithm, MOESI cache coherence protocol), but when he is asked during a job interview to implement something straightforward (like a serial adder with valid and last signals, or a static pipeline to compute a formula with dependencies between the pipelined blocks) many struggle with such tasks.<\/p>\n

In my opinion it is a bad idea to teach from high-level (Tomasulo and MESI models) to low-level (Verilog implementation) because on the transaction level a student does not have intuition about static timing analysis, does not have knowledge of how to verify the corner cases of what he designs, does not know how to measure the bandwidth etc. It is better to start from simple sequential logic tasks, then static pipelines, master them well, add flow control (including credit counters), and move to something more complicated. A person who knows only how to write very trivial things in Verilog (like a simple mux or an FSM) and can talk about superscalar CPUs — has very limited use in the industry, so you need to practically master the things in the middle.<\/p>\n

There is no silver bullet and no way to skip SystemVerilog RTL exercises. High-level synthesis (C algorithms — to — hardware translation) was never adopted into the mainstream, new languages (Chisel, etc) do not substitute knowledge of sequential logic behavior, ChatGPT writes nonsense etc. If you want to design hardware for AI, or work in hardware to accelerate text search, DSP or graphics, you cannot skip the exercises with sequential logic, pipelines, FIFOs etc.<\/p>\n

So the next steps are:<\/strong><\/p>\n

1) We are going to do Zoom call on each Sunday starting March 24, 2024 at 11 am California time (summer time). The link.<\/a> During this call we are going to discuss the SystemVerilog Homework and the individual projects.<\/p>\n

2) Once we get more materials, we are going to organize Show-and-Tell sessions in Hacker Dojo, for a wider audience. During the session several participants from the core team will present demos on various FPGA boards and explain to the curious how FPGA and ASIC work.<\/p>\n

Now I would like to copy a fragment of the previous post «Verilog Meetups @ Hacker Dojo: the status and the plans for February 2024»<\/a> which has all the necessary links and a list of the recommended literature:<\/p>\n

Self Education to Guarantee the Quality<\/strong><\/p>\n

To ensure everybody’s quality, we expect every member who is new to the field, to go through the following steps in his education. Those who already know the basics can review the materials to ensure their quality:<\/p>\n

    \n
  1. \n

    Do all the homework from\u00a0https:\/\/github.com\/yuri-panchul\/systemverilog-homework<\/a>.<\/p>\n<\/li>\n

  2. \n

    Run and review all the examples in\u00a0https:\/\/github.com\/yuri-panchul\/basics-graphics-music<\/a><\/p>\n<\/li>\n

  3. \n

    Get a tutorial in Bash if you have not done this before. We use Bash scripts to isolate users from vendor-specific toolchains.<\/p>\n<\/li>\n

  4. \n

    Get a tutorial in Git if you have not done this before. We use Git and GitHub Forks \/ Pull requests as the vehicle of collaboration inside the team and to publish the examples.<\/p>\n<\/li>\n

  5. \n

    Get a tutorial in Markdown markup language as we use it for documentation.<\/p>\n<\/li>\n

  6. \n

    Study a diagram editor for microarchitecture diagrams such as Lucidspark or draw.io.<\/p>\n<\/li>\n

  7. \n

    Learn how to use\u00a0wavedrom.com<\/a>\u00a0for microarchitecture diagrams.<\/p>\n<\/li>\n

  8. \n

    Learn how to use\u00a0edaplayground.com<\/a>\u00a0useful to create verification examples with full-featured SystemVerilog.<\/p>\n<\/li>\n<\/ol>\n

    The Recommended Literature<\/strong><\/p>\n

    In parallel with going through the problems and examples, we recommend studying the following books and online articles:<\/p>\n

      \n
    1. \n

      Digital Design and Computer Architecture, RISC-V Edition by Sarah Harris and David Harris<\/a>.<\/p>\n<\/li>\n

    2. \n

      Logic Design and Verification Using SystemVerilog \u2013 March 1, 2016 by Donald Thomas<\/a>. Not to be confused with the old (starting 1980s) books of the same author.<\/p>\n<\/li>\n

    3. \n

      Digital Design: A Systems Approach by William James Dally and R. Curtis Harting<\/a>.<\/p>\n<\/li>\n

    4. \n

      IEEE 1800-2017 — Standard for SystemVerilog<\/a>\u00a0should be used as a reference.<\/p>\n<\/li>\n

    5. \n

      Verilog Gotcha articles by Stuart Sutherland, Don Mills and Chris Spear:\u00a0Part 1<\/a>\u00a0and\u00a0Part 2<\/a>.<\/p>\n<\/li>\n

    6. \n

      The articles of Cliff Cummings<\/a>.<\/p>\n

      Once we get to verification examples:<\/p>\n<\/li>\n

    7. \n

      SystemVerilog for Verification: A Guide to Learning the Testbench Language Features 3rd ed. 2012 Edition by Chris Spear and Greg Tumbush<\/a>.<\/p>\n<\/li>\n

    8. \n

      Writing Testbenches using SystemVerilog 2006th Edition by Janick Bergeron<\/a>.<\/p>\n<\/li>\n

    9. \n

      Getting Started with UVM: A Beginner’s Guide<\/a>\u00a0— May 22, 2013 by Vanessa R. Cooper. This book does an excellent job of setting up the minimum necessary skeleton for the UVM testbench. However, the BFM driver code in this book is not good for pipelined and out-of-order protocols. There are no good books on BFMs for pipelined and out-of-order protocols — we have examples of how to do this right\u00a0here<\/a>, but we need to convert this example into UVM using Vanessa R. Cooper’s UVM skeleton example.<\/p>\n

      Once we get to CPU-specific examples (like branch predictors, caches and Tomasulo), we recommend:<\/p>\n<\/li>\n

    10. \n

      Modern Processor Design: Fundamentals of Superscalar Processors by John Paul Shen and Mikko H. Lipasti.<\/a><\/p>\n<\/li>\n

    11. \n

      Modern System-on-Chip Design by David J. Greaves<\/a>.<\/p>\n<\/li>\n<\/ol>\n

      Talk to you on Sunday’s Zoom call at 11 am California time (summer time) — The link.<\/a> During this call we are going to discuss the SystemVerilog Homework and the individual projects.<\/p>\n<\/p>\n<\/div>\n<\/div>\n<\/div>\n

      <\/div>\n


      \u0441\u0441\u044b\u043b\u043a\u0430 \u043d\u0430 \u043e\u0440\u0438\u0433\u0438\u043d\u0430\u043b \u0441\u0442\u0430\u0442\u044c\u0438       https:\/\/habr.com\/ru\/articles\/802117\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

      <\/div>\n
      \n
      \n
      \n
      \n
      <\/figure>\n

      Since the New Year we had 7 Verilog meetups<\/a> at HackerDojo<\/a>. We discussed the modern way of designing digital circuits using hardware description languages, the exercises on FPGA boards and the topic of microarchitecture. For the last two sessions we went over the most basic CPU core that can be used as a baseline for further exercises.<\/p>\n

      There are video recordings available for some meetups and Zoom calls<\/a>. Particularly I recommend to see the first<\/a> video (it gives a general overview) and a video about a baseline CPU core <\/a>we can use for a number of exercises.<\/p>\n

      From the beginning we planned to split the meetups into two types of sessions:<\/strong><\/p>\n

      1.Regular meetings of a small R&D team that develops multiple open-source repositories of SystemVerilog examples. Two focuses: compatibility (boards, ASIC and FPGA toolchains, peripherals) and microarchitecture (what the electronic companies ask you during a job interview — pipelines, FIFO queues, arbiters etc).<\/p>\n

      2) Occasional Show-and-Tell sessions for a wider audience interested in reconfigurable hardware as a way of computing different from software. Displaying graphics and recognizing music using FPGA boards, together with some presentations from the members of the regular R&D meetings: How do FPGAs work? What is their role in the electronic industry? How is it related to mass-market electronic devices? Can you make your own ASIC (Tiny Tapeout, OpenLane, eFabless etc)?<\/p>\n

      During the meetups there were three kinds of participants:<\/strong><\/p>\n

      1) People who are curious about the technology but not interested in doing exercises. This is the prime audience for show-and-tell sessions.<\/p>\n

      2) People who are interested in learning new things to get additional career options. They can take some projects, but they may not be interested in coming every Sunday. Many prefer to work at home and communicate via email or Zoom.<\/p>\n

      3) People who already work in the field (like CPU designers) who can be interested in more advanced material (like new branch predictors or design verification techniques for multithreading), but who get bored when the discussion moves around basic topics or discussions about the example infrastructure (pins, toolchain details).<\/p>\n

      On the necessity of doing exercises<\/strong><\/p>\n

      At this moment, in order to make progress toward both goals (implementing new examples and show-and-tell sessions) it is essential for the regular participants (mostly from group 2) to solve all the homework exercises (see the list here) in parallel with studying the recommended materials. I can review the results over the internet and during Zoom sessions.<\/p>\n

      There is no other way. I can spend a year talking, but if a listener does not do the exercises, there is no progress. In fact it happens all the time with recent college graduates: a graduate may have in his resume some sophisticated microarchitectural things (Tomasulo algorithm, MOESI cache coherence protocol), but when he is asked during a job interview to implement something straightforward (like a serial adder with valid and last signals, or a static pipeline to compute a formula with dependencies between the pipelined blocks) many struggle with such tasks.<\/p>\n

      In my opinion it is a bad idea to teach from high-level (Tomasulo and MESI models) to low-level (Verilog implementation) because on the transaction level a student does not have intuition about static timing analysis, does not have knowledge of how to verify the corner cases of what he designs, does not know how to measure the bandwidth etc. It is better to start from simple sequential logic tasks, then static pipelines, master them well, add flow control (including credit counters), and move to something more complicated. A person who knows only how to write very trivial things in Verilog (like a simple mux or an FSM) and can talk about superscalar CPUs — has very limited use in the industry, so you need to practically master the things in the middle.<\/p>\n

      There is no silver bullet and no way to skip SystemVerilog RTL exercises. High-level synthesis (C algorithms — to — hardware translation) was never adopted into the mainstream, new languages (Chisel, etc) do not substitute knowledge of sequential logic behavior, ChatGPT writes nonsense etc. If you want to design hardware for AI, or work in hardware to accelerate text search, DSP or graphics, you cannot skip the exercises with sequential logic, pipelines, FIFOs etc.<\/p>\n

      So the next steps are:<\/strong><\/p>\n

      1) We are going to do Zoom call on each Sunday starting March 24, 2024 at 11 am California time (summer time). The link.<\/a> During this call we are going to discuss the SystemVerilog Homework and the individual projects.<\/p>\n

      2) Once we get more materials, we are going to organize Show-and-Tell sessions in Hacker Dojo, for a wider audience. During the session several participants from the core team will present demos on various FPGA boards and explain to the curious how FPGA and ASIC work.<\/p>\n

      Now I would like to copy a fragment of the previous post «Verilog Meetups @ Hacker Dojo: the status and the plans for February 2024»<\/a> which has all the necessary links and a list of the recommended literature:<\/p>\n

      Self Education to Guarantee the Quality<\/strong><\/p>\n

      To ensure everybody’s quality, we expect every member who is new to the field, to go through the following steps in his education. Those who already know the basics can review the materials to ensure their quality:<\/p>\n

        \n
      1. \n

        Do all the homework from\u00a0https:\/\/github.com\/yuri-panchul\/systemverilog-homework<\/a>.<\/p>\n<\/li>\n

      2. \n

        Run and review all the examples in\u00a0https:\/\/github.com\/yuri-panchul\/basics-graphics-music<\/a><\/p>\n<\/li>\n

      3. \n

        Get a tutorial in Bash if you have not done this before. We use Bash scripts to isolate users from vendor-specific toolchains.<\/p>\n<\/li>\n

      4. \n

        Get a tutorial in Git if you have not done this before. We use Git and GitHub Forks \/ Pull requests as the vehicle of collaboration inside the team and to publish the examples.<\/p>\n<\/li>\n

      5. \n

        Get a tutorial in Markdown markup language as we use it for documentation.<\/p>\n<\/li>\n

      6. \n

        Study a diagram editor for microarchitecture diagrams such as Lucidspark or draw.io.<\/p>\n<\/li>\n

      7. \n

        Learn how to use\u00a0wavedrom.com<\/a>\u00a0for microarchitecture diagrams.<\/p>\n<\/li>\n

      8. \n

        Learn how to use\u00a0edaplayground.com<\/a>\u00a0useful to create verification examples with full-featured SystemVerilog.<\/p>\n<\/li>\n<\/ol>\n

        The Recommended Literature<\/strong><\/p>\n

        In parallel with going through the problems and examples, we recommend studying the following books and online articles:<\/p>\n

          \n
        1. \n

          Digital Design and Computer Architecture, RISC-V Edition by Sarah Harris and David Harris<\/a>.<\/p>\n<\/li>\n

        2. \n

          Logic Design and Verification Using SystemVerilog \u2013 March 1, 2016 by Donald Thomas<\/a>. Not to be confused with the old (starting 1980s) books of the same author.<\/p>\n<\/li>\n

        3. \n

          Digital Design: A Systems Approach by William James Dally and R. Curtis Harting<\/a>.<\/p>\n<\/li>\n

        4. \n

          IEEE 1800-2017 — Standard for SystemVerilog<\/a>\u00a0should be used as a reference.<\/p>\n<\/li>\n

        5. \n

          Verilog Gotcha articles by Stuart Sutherland, Don Mills and Chris Spear:\u00a0Part 1<\/a>\u00a0and\u00a0Part 2<\/a>.<\/p>\n<\/li>\n

        6. \n

          The articles of Cliff Cummings<\/a>.<\/p>\n

          Once we get to verification examples:<\/p>\n<\/li>\n

        7. \n

          SystemVerilog for Verification: A Guide to Learning the Testbench Language Features 3rd ed. 2012 Edition by Chris Spear and Greg Tumbush<\/a>.<\/p>\n<\/li>\n

        8. \n

          Writing Testbenches using SystemVerilog 2006th Edition by Janick Bergeron<\/a>.<\/p>\n<\/li>\n

        9. \n

          Getting Started with UVM: A Beginner’s Guide<\/a>\u00a0— May 22, 2013 by Vanessa R. Cooper. This book does an excellent job of setting up the minimum necessary skeleton for the UVM testbench. However, the BFM driver code in this book is not good for pipelined and out-of-order protocols. There are no good books on BFMs for pipelined and out-of-order protocols — we have examples of how to do this right\u00a0here<\/a>, but we need to convert this example into UVM using Vanessa R. Cooper’s UVM skeleton example.<\/p>\n

          Once we get to CPU-specific examples (like branch predictors, caches and Tomasulo), we recommend:<\/p>\n<\/li>\n

        10. \n

          Modern Processor Design: Fundamentals of Superscalar Processors by John Paul Shen and Mikko H. Lipasti.<\/a><\/p>\n<\/li>\n

        11. \n

          Modern System-on-Chip Design by David J. Greaves<\/a>.<\/p>\n<\/li>\n<\/ol>\n

          Talk to you on Sunday’s Zoom call at 11 am California time (summer time) — The link.<\/a> During this call we are going to discuss the SystemVerilog Homework and the individual projects.<\/p>\n<\/p>\n<\/div>\n<\/div>\n<\/div>\n

          <\/div>\n


          \u0441\u0441\u044b\u043b\u043a\u0430 \u043d\u0430 \u043e\u0440\u0438\u0433\u0438\u043d\u0430\u043b \u0441\u0442\u0430\u0442\u044c\u0438           https:\/\/habr.com\/ru\/articles\/802117\/<\/a>
          <\/br><\/br><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-371521","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts\/371521","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=371521"}],"version-history":[{"count":0,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts\/371521\/revisions"}],"wp:attachment":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=371521"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=371521"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=371521"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}