renameHEADmaster

1 files changed, 0 insertions, 48 deletions

diff --git a/_posts/2026-01-06-getting-started-with-my-fpga-board-and-verilog.md b/_posts/2026-01-06-getting-started-with-my-fpga-board-and-verilog.md
deleted file mode 100644
index da08908..0000000
--- a/_posts/2026-01-06-getting-started-with-my-fpga-board-and-verilog.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-layout: post
-title: Getting started with my FPGA board and Verilog
-date: 2026-01-06 15:52 +0100
-categories: tech
-lang: en
----
-
-After I got my [FPGA dev board]({% post_url 2025-12-26-fpga-dev-board %}), I
-have several books in my virtual library (Humble Bundle etc.) and decided to
-start with Verilog. The book contained a few exercises which I tried to
-implement. After getting a feeling for the language - which took some time to be
-honest - my second step was to implement the CPU from
-[Nandgame](https://nandgame.com/). (1)
-
-I actually even thought about writing an assembler for the "machine" (2).  But
-then again, I only tested the CPU and the Verilog modules in test benches so
-far.  I haven't loaded anything of that on my dev board, nor did I think about
-how I can "properly" simulate the CPU, including "loading" a program and viewing
-its state.
-
-I *think* I need to play around with Verilator for that, which allows
-translating Verilog code to C++. This way, I should be able to control the CPU
-and also view its state.  I'll take a look at
-[nand2tetris](https://www.nand2tetris.org/), which, to my knowledge, also
-contains a section about that topic. Its architecture is similar, though it uses
-a different instruction set.
-
-Even playing Nandgame the first time - way back then - gave me a good insight on
-how CPUs work.  Implementing one in Verilog makes things click further.  Well,
-at least for simple architectures. I still have no idea how pipelining works,
-and all the details that entails, nor how multi-cycle-instructions work.  That's
-probably for another time.
-
-You can view the code I wrote so far [in my git
-repository](https://git.uvok.de/fpga-exper/tree/?h=main).
-
-(1) Tools that helped me were Icarus Verilog, Verilator and GTKwave, which are
-all contained on the [OSS CAD
-Suite](https://github.com/YosysHQ/oss-cad-suite-build).  That is, both linting
-and test benches.
-
-(2) So I started with writing a disassembler first. I wanted to develop a nice
-syntax first, because I don't like the syntax nand2tetris introduces. That's not
-"proper assembler" for me. One of the special things of the architecture is that
-you can have multiple "destinations" for an operation, though - or none at all.
-To my shame, I used an LLM to get inspiration how the language could look like. 
-