Welcome. This course is built so a curious beginner can start from zero chip experience and finish able to write, simulate, and defend real RTL β ending with an I2C controller capstone. You do not need a company EDA license to begin.
By the end, you will understand the full VLSI map, write clean Verilog, catch common bugs with lint/CDC/timing thinking, verify your work, and ship an I2C design you can show in interviews.
You know basic digital ideas (or are willing to learn Module 2) and want a clear path into RTL jobs.
You write software or firmware and want to understand how hardware RTL is actually designed and reviewed.
You already write some Verilog but want stronger habits: lint, CDC awareness, timing/area thinking, and clean FSMs.
You want structured practice plus a real protocol project (I2C) instead of random tutorial scraps.
You do not need Synopsys/Cadence tools, an FPGA board, or prior SystemVerilog. Verilog-first is enough for this course; SV ideas appear later where they help.
Prerequisites self-check β be honest. A "no" is fine; the course will teach it.
| Skill | Minimum needed | If you're weak here |
|---|---|---|
| Binary / hex | Know 0/1, count in binary to 15 | Module 2 covers this from scratch |
| Logic gates | AND, OR, NOT, XOR at a high level | Module 2 + free DE pages on EcrioniX |
| Programming | Any language β variables, loops, functions | Helps with testbenches; not required day one |
| Electronics | None required | We explain clocks/resets when they matter |
| Math | Basic algebra | Enough for timing/area intuition later |
Trap: "I need a EE degree first." Many strong RTL engineers came from CS, physics, or self-study. Consistency beats credentials at the learning stage.
Every lesson in this course follows the same learning loop. Treat it like a recipe β don't skip steps.
One lesson β one full loop. Capstone = many loops on the same design.
| Step | Time (typical) | Done when⦠|
|---|---|---|
| First read | 8β12 min | You can summarize the lesson in one sentence |
| Trap box | 3β5 min | You can name the mistake without looking |
| Type + sim | 15β30 min | Compile clean; waves match your prediction |
| 3 bullets | 3 min | Written before you open the next lesson |
RTL is like learning a musical instrument. Watching someone play is not practice. Your hands (typing + simulating) are the practice. Scales are boring; they are also why professionals sound effortless.
Common trap: binge-reading five lessons without simulating. You will feel smart for an hour and forget everything by tomorrow. One lesson + sim beats five lessons + scroll.
Plan for 45β90 minutes per study day. Below is a sample week for someone working or in school full-time.
| Day | Focus | Example tasks |
|---|---|---|
| Mon | New lesson | Read Module 3 lesson + type starter code |
| Tue | Sim lab | Run TB, fix compile errors, screenshot waves |
| Wed | New lesson | Read next lesson; note one trap box |
| Thu | Review | Re-read Mon notes; change one line and re-sim |
| Fri | Light / catch-up | Finish bullets or redo a failed lab |
| Weekend | Optional deep dive | Capstone planning, extra challenges, or rest |
Your two permanent tools are the online simulator and a single notes file (Notion, Google Doc, or paper). Link them:
Template header for your notes doc: Lesson | Date | Learned | Confused | Next | Senior would reject ifβ¦
| Cluster | Modules | You know you're on track when⦠|
|---|---|---|
| Orientation | 0β1 | You can draw Spec β RTL β PD on a napkin and name who owns each step |
| Foundations | 2β3 | You write a flop + simple TB without looking up syntax every line |
| Building blocks | 4β5 | You spot blocking vs non-blocking mistakes in someone else's code |
| Control + perf | 6β8 | You draw an FSM bubble diagram before writing case(state) |
| Industry quality | 9 | You run a mental lint/CDC pass on every new module |
| Verify + ship | 10β11 | You can demo I2C start/stop/ACK on waves and defend your checklist |
| Career | 12 | You tell a 2-minute "Spec β waves" story in an interview |
Simulation proves one scenario. Reviewers ask about reset, corners, synthesis, and maintainability.
Parallel hardware, not sequential software. Time and clocks are first-class.
Companies hire people who already simulate and read waves. This course builds that habit free.
Without Module 1 context, you won't know why DFT, timing, or sign-off matter to your RTL style.
A lesson is complete when you can do all three:
Rubric with examples:
| Criterion | Not done | Done |
|---|---|---|
| Explain | "It's about flops" (vague) | "A flop samples D on posedge clk; async reset forces Q to 0 when rst_n is low" |
| Simulate | Copied code, never ran | Changed reset polarity once; saw expected failure; fixed it |
| Trap | Can't name a bug | "Blocking assignment in sequential always β sim/synth mismatch" |
Honest check: if you skipped the simulator for this lesson, you are not done β even if you read every word. Go back to Lesson 0.2 and run the smoke test.