Repository navigation
Expand file tree
/
Copy pathindex.xml
More file actions
278 lines (241 loc) · 20.6 KB
/
Copy pathindex.xml
File metadata and controls
278 lines (241 loc) · 20.6 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Home on Vaisakh N V</title><link>https://vaisakhnv.com/</link><description>Recent content in Home on Vaisakh N V</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate><atom:link href="https://vaisakhnv.com/index.xml" rel="self" type="application/rss+xml"/><item><title>About</title><link>https://vaisakhnv.com/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vaisakhnv.com/about/</guid><description><div class="ui-abstract" data-reveal>
<div class="ui-abstract-kicker">Spec (who I am and what I build)</div>
<div class="ui-abstract-body">
I’m <strong>Vaisakh Naduvodi Viswambharan</strong>, a Master’s student in <strong>Nanoelectronic Systems at TU Dresden</strong>.<br>
My focus is <strong>digital IC design and verification</strong>, and I build <strong>GenAI-assisted tooling</strong> to make verification workflows faster, more systematic, and easier to scale—without losing rigor.
</div>
</div>
<div class="ui-metrics" data-reveal>
<div class="ui-metrics-grid">
<ul>
<li><strong>Domains:</strong> Formal · UVM · RTL · RISC-V · Floating-point</li>
<li><strong>What I optimize for:</strong> proof structure, coverage discipline, and repeatable engineering workflows</li>
<li><strong>Where to look next:</strong> <strong>Projects</strong> for artifacts, <strong>Publications</strong> for academic evidence, <strong>Contact</strong> for collaboration</li>
</ul>
</div>
</div>
<h2 id="what-im-working-on-now">What I’m working on now</h2>
<p>My thesis explores how AI can help turn design intent into reliable verification results with less manual iteration. In parallel, I’m building <strong>SaxoFlow</strong>, a student-focused initiative combining <strong>AI-assisted workflows</strong> with <strong>open-source EDA tools</strong>.</p></description></item><item><title>Contact</title><link>https://vaisakhnv.com/contact/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vaisakhnv.com/contact/</guid><description><div class="ui-abstract" data-reveal>
<div class="ui-abstract-kicker">Interface (how to reach me)</div>
<div class="ui-abstract-body">
<p>If you want to connect about a <strong>PhD opportunity</strong>, <strong>research collaboration</strong>, or a <strong>digital design/verification role</strong> (especially where GenAI is used seriously), reach out.</p>
<p>I respond fastest on <strong>email</strong> and <strong>LinkedIn</strong>.</p>
</div>
</div>
<div class="ui-metrics" data-reveal>
<div class="ui-metrics-grid">
<ul>
<li><strong>Primary:</strong> Email · LinkedIn</li>
<li><strong>Evidence:</strong> Publications · Case studies · GitHub artifacts</li>
</ul>
</div>
</div>
<h2 id="direct-contact">Direct contact</h2>
<article class="ui-artifact ui-card" data-reveal><a class="ui-artifact-link" href="mailto:vaisakh.viswam96@gmail.com"><header class="ui-artifact-header">
<h3 class="ui-h3 ui-artifact-title">Email</h3><p class="ui-meta">Best for roles, PhD discussions, and collaboration proposals</p></header>
<div class="ui-artifact-body">
<a href="mailto:vaisakh.viswam96@gmail.com">vaisakh.viswam96@gmail.com</a>
</div><div class="ui-tags" aria-label="Tags"><span class="ui-tag">Fast response</span><span class="ui-tag">Direct</span></div><div class="ui-artifact-cta">Send email →</div></a></article>
<article class="ui-artifact ui-card" data-reveal><a class="ui-artifact-link" href="https://www.linkedin.com/in/vaisakh-naduvodi-viswambharan-1045b3138/"><header class="ui-artifact-header">
<h3 class="ui-h3 ui-artifact-title">LinkedIn</h3><p class="ui-meta">Best for introductions and recruiter outreach</p></description></item><item><title>Experience</title><link>https://vaisakhnv.com/experience/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vaisakhnv.com/experience/</guid><description><div class="ui-abstract" data-reveal>
<div class="ui-abstract-kicker">Implement (roles, ownership, outcomes)</div>
<div class="ui-abstract-body">
I care about <strong>verification quality</strong> and <strong>repeatable engineering workflows</strong>.<br>
These roles summarize what I owned, what I shipped, and the kind of problems I’m trusted with.
</div>
</div>
<div class="ui-metrics" data-reveal>
<div class="ui-metrics-grid">
<ul>
<li><strong>Resume:</strong> /resume/VaisakhNaduvodiViswambharan.pdf</li>
<li><strong>Core focus:</strong> Digital verification · formal/coverage thinking · automation · GenAI-assisted workflows</li>
</ul>
</div>
</div>
<h2 id="roles">Roles</h2>
<article class="ui-artifact ui-card" data-reveal><header class="ui-artifact-header">
<h3 class="ui-h3 ui-artifact-title">Infineon Technologies (Dresden, Germany) — Digital Functional Verification Intern</h3><p class="ui-meta">Oct 2024–present</p></header>
<div class="ui-artifact-body">
<p><strong>What I did</strong></p>
<ul>
<li>Researched AI/ML approaches to improve digital verification workflows</li>
<li>Built a Python-based automation framework for RTL design, testbench generation, and formal property verification (agentic AI)</li>
<li>Executed formal verification on representative blocks (e.g., floating-point adder, FIFO) and functional verification of an ALU using UVM</li>
</ul>
<p><strong>What I optimize for</strong></p></description></item><item><title>Floating-point formal verification</title><link>https://vaisakhnv.com/case-studies/floating-point-formal/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vaisakhnv.com/case-studies/floating-point-formal/</guid><description><div class="ui-abstract" data-reveal>
<div class="ui-abstract-kicker">Case study (formal verification)</div>
<div class="ui-abstract-body">
A scalable floating-point verification workflow using RTL-to-RTL model checking against a golden reference, structured into staged helper assertions to make proofs converge.
</div>
</div>
<div class="ui-metrics" data-reveal>
<div class="ui-metrics-grid">
<ul>
<li><strong>Focus:</strong> proof structure · helper lemmas · counterexample-guided refinement</li>
<li><strong>Domains:</strong> floating-point · arithmetic · correctness-critical blocks</li>
<li><strong>Stack:</strong> SystemVerilog · SVA · formal tooling · Python automation</li>
</ul>
</div>
</div>
<h2 id="problem">Problem</h2>
<p>Floating-point units are correctness-critical and difficult to cover comprehensively with simulation alone. Formal proofs often fail without a disciplined decomposition strategy.</p></description></item><item><title>Formal verification</title><link>https://vaisakhnv.com/topics/formal-verification/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vaisakhnv.com/topics/formal-verification/</guid><description><div class="ui-abstract" data-reveal>
<div class="ui-abstract-kicker">Topic (verification)</div>
<div class="ui-abstract-body">
Formal verification is how I turn design intent into <strong>provable evidence</strong>. My approach is pragmatic: focus on proof structure, build helper assertions, and iterate using counterexamples and coverage signals.
</div>
</div>
<div class="ui-metrics" data-reveal>
<div class="ui-metrics-grid">
<ul>
<li><strong>Focus:</strong> proof structure · convergence · evidence trail</li>
<li><strong>Methods:</strong> helper lemmas · CEX-guided refinement · coverage-aware iteration</li>
</ul>
</div>
</div>
<h2 id="what-i-optimize-for">What I optimize for</h2>
<ul>
<li><strong>Fast convergence:</strong> break big goals into smaller provable claims</li>
<li><strong>Explainable failures:</strong> counterexamples should point to actionable causes</li>
<li><strong>Repeatability:</strong> artifacts, logs, and assumptions are preserved so results can be reproduced</li>
</ul>
<h2 id="typical-workflow">Typical workflow</h2>
<ol>
<li><strong>Scope the intent:</strong> what must be true (and under which assumptions)</li>
<li><strong>Define the interface:</strong> clocks/resets/handshakes; avoid underspecified properties</li>
<li><strong>Decompose:</strong> create a staged plan (invariants / helper lemmas first)</li>
<li><strong>Run and refine:</strong> use counterexamples to repair constraints and properties</li>
<li><strong>Measure evidence:</strong> coverage/vacuity checks; avoid “proved but meaningless”</li>
</ol>
<h2 id="where-this-shows-up-on-my-site">Where this shows up on my site</h2>
<ul>
<li>Floating-point case study: proof decomposition + refinement</li>
<li>Publications: canonical paper links and write-ups</li>
</ul>
<section class="ui-cta ui-card" data-reveal>
<h2 class="ui-h2">Want to discuss a formal verification problem?</h2>
<p class="ui-muted">If you want to collaborate, discuss roles, or review artifacts, reach out.</p></description></item><item><title>GenAI for EDA</title><link>https://vaisakhnv.com/topics/genai-for-eda/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vaisakhnv.com/topics/genai-for-eda/</guid><description><div class="ui-abstract" data-reveal>
<div class="ui-abstract-kicker">Topic (workflows)</div>
<div class="ui-abstract-body">
I use GenAI where it creates leverage: generating structured artifacts, accelerating iteration loops, and reducing repetitive engineering work—while keeping an evidence trail so results remain trustworthy.
</div>
</div>
<div class="ui-metrics" data-reveal>
<div class="ui-metrics-grid">
<ul>
<li><strong>Goal:</strong> faster iteration without losing rigor</li>
<li><strong>Approach:</strong> tool-centric pipelines · structured artifacts · reproducibility</li>
</ul>
</div>
</div>
<h2 id="what-i-believe-works-and-what-doesnt">What I believe works (and what doesn’t)</h2>
<p><strong>Works</strong></p>
<ul>
<li>Constraining generation with <strong>structured schemas</strong></li>
<li>Grounding with <strong>project context</strong> (specs, IRs, signal allowlists)</li>
<li>Using LLMs for <strong>draft → critique → repair</strong> loops with tooling in the loop</li>
</ul>
<p><strong>Doesn’t</strong></p></description></item><item><title>Projects</title><link>https://vaisakhnv.com/projects/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vaisakhnv.com/projects/</guid><description><div class="ui-abstract" data-reveal>
<div class="ui-abstract-kicker">Blocks (what I build and ship)</div>
<div class="ui-abstract-body">
This page highlights projects that represent what I want to be known for: <strong>digital chip design</strong>, <strong>verification</strong>, and <strong>practical use of GenAI</strong> in engineering workflows.<br>
Each item is written as an artifact: what it is, what I owned, and what evidence exists.
</div>
</div>
<h2 id="featured">Featured</h2>
<article class="ui-artifact ui-card" data-reveal><a class="ui-artifact-link" href="https://vaisakhnv.com/case-studies/saxoflow/"><header class="ui-artifact-header">
<h3 class="ui-h3 ui-artifact-title">SaxoFlow — Open-source design &#43; verification suite (AI-assisted)</h3><p class="ui-meta">Aug 2025–present · Personal / open-source</p></header>
<div class="ui-artifact-body">
<p>SaxoFlow reduces setup friction and repetitive work by combining open-source EDA tools with GenAI-assisted workflows.</p></description></item><item><title>Publications</title><link>https://vaisakhnv.com/publications/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vaisakhnv.com/publications/</guid><description><div class="ui-abstract" data-reveal>
<div class="ui-abstract-kicker">Evidence (papers, venues, artifacts)</div>
<div class="ui-abstract-body">
This page lists published and accepted research work. Each entry is written as a <strong>mini-paper</strong>: venue context, contribution summary, and artifact links.
</div>
</div>
<div class="ui-metrics" data-reveal>
<div class="ui-metrics-grid">
<ul>
<li><strong>Google Scholar:</strong> <a href="https://scholar.google.com/citations?user=d1vnfGEAAAAJ&amp;hl=en">https://scholar.google.com/citations?user=d1vnfGEAAAAJ&amp;hl=en</a></li>
<li><strong>ORCID:</strong> <a href="https://orcid.org/0009-0002-1101-1285">https://orcid.org/0009-0002-1101-1285</a></li>
</ul>
</div>
</div>
<h2 id="2025">2025</h2>
<article class="ui-artifact ui-card" data-reveal><a class="ui-artifact-link" href="https://ieeexplore.ieee.org/document/11218681"><header class="ui-artifact-header">
<h3 class="ui-h3 ui-artifact-title">Hey AI, Generate Me a Hardware Code! Agentic AI-based Hardware Design &amp; Verification</h3><p class="ui-meta">Conference paper (IEEE / SBCCI) · 31 Oct 2025</p></header>
<div class="ui-artifact-body">
<p>An agent-based approach to hardware design and verification that combines AI agents with human-in-the-loop iteration to converge toward working verification flows.</p></description></item><item><title>RISC-V “Kreacher”</title><link>https://vaisakhnv.com/case-studies/riscv-kreacher/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vaisakhnv.com/case-studies/riscv-kreacher/</guid><description><div class="ui-abstract" data-reveal>
<div class="ui-abstract-kicker">Case study (RTL &#43; integration)</div>
<div class="ui-abstract-body">
A collaborative RISC-V processor integrated into a SoC environment, with contributions focused on datapath correctness and clean integration interfaces.
</div>
</div>
<div class="ui-metrics" data-reveal>
<div class="ui-metrics-grid">
<ul>
<li><strong>Scope:</strong> datapath modules · integration boundaries · correctness discipline</li>
<li><strong>Stack:</strong> SystemVerilog · RTL integration workflow</li>
<li><strong>Note:</strong> code is not public (team project)</li>
</ul>
</div>
</div>
<h2 id="problem">Problem</h2>
<p>SoC integration requires stable interfaces, disciplined block boundaries, and correctness-first implementation to avoid late-stage integration regressions.</p>
<h2 id="approach">Approach</h2>
<ul>
<li>Implemented datapath modules including ALU and decoder</li>
<li>Focused on functional accuracy and clean integration</li>
<li>Kept interfaces predictable for SoC-level bring-up</li>
</ul>
<h2 id="evidence">Evidence</h2>
<p>Work product exists as team integration deliverables (code not public). I can share details that are safe to discuss.</p></description></item><item><title>SaxoFlow</title><link>https://vaisakhnv.com/case-studies/saxoflow/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vaisakhnv.com/case-studies/saxoflow/</guid><description><div class="ui-abstract" data-reveal>
<div class="ui-abstract-kicker">Case study (open-source tooling)</div>
<div class="ui-abstract-body">
SaxoFlow is an evidence-first design + verification workflow that combines open-source EDA tools with GenAI-assisted generation and iteration loops—built to make learning and prototyping faster and more systematic.
</div>
</div>
<div class="ui-metrics" data-reveal>
<div class="ui-metrics-grid">
<ul>
<li><strong>Focus:</strong> verification workflow automation + reproducibility</li>
<li><strong>Stack:</strong> Python · SystemVerilog · SVA · open-source EDA ecosystem</li>
<li><strong>Artifacts:</strong> CLI flows · agent-assisted generation · logs/evidence trail</li>
</ul>
</div>
</div>
<h2 id="problem">Problem</h2>
<p>Digital design and verification iteration is slowed down by environment setup, tool fragmentation, and repeated manual loops (install → run → debug → re-run).</p></description></item><item><title>SystemVerilog and SVA</title><link>https://vaisakhnv.com/topics/systemverilog-sva/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vaisakhnv.com/topics/systemverilog-sva/</guid><description><div class="ui-abstract" data-reveal>
<div class="ui-abstract-kicker">Topic (properties)</div>
<div class="ui-abstract-body">
SVA is not just syntax—good assertions encode intent precisely, resist vacuity, and scale with a proof plan. I write SVA with explicit assumptions, clear temporal structure, and reusable patterns.
</div>
</div>
<div class="ui-metrics" data-reveal>
<div class="ui-metrics-grid">
<ul>
<li><strong>Principles:</strong> clarity · vacuity resistance · minimal assumptions</li>
<li><strong>Patterns:</strong> interface contracts · invariants · refinement lemmas</li>
</ul>
</div>
</div>
<h2 id="what-good-sva-means-in-practice">What “good SVA” means in practice</h2>
<ul>
<li><strong>Signal discipline:</strong> assertions reference stable, meaningful signals (not accidental internals)</li>
<li><strong>Temporal intent:</strong> preconditions and consequences are separated clearly</li>
<li><strong>Assumptions are explicit:</strong> environment constraints are documented and reviewable</li>
<li><strong>Vacuity checks:</strong> proved properties should still be <em>informative</em></li>
</ul>
<h2 id="common-patterns-i-use">Common patterns I use</h2>
<ul>
<li><strong>Interface contracts:</strong> request/ack, ready/valid, FIFO rules</li>
<li><strong>Safety properties:</strong> “this bad thing never happens”</li>
<li><strong>Liveness under assumptions:</strong> “eventually” properties only where appropriate</li>
<li><strong>Helper lemmas:</strong> small provable stepping stones for complex end-to-end goals</li>
</ul>
<h2 id="where-this-shows-up-on-my-site">Where this shows up on my site</h2>
<ul>
<li>Formal case studies (proof structure)</li>
<li>Publications (property strategy and evaluation)</li>
</ul>
<section class="ui-cta ui-card" data-reveal>
<h2 class="ui-h2">Need help structuring assertions for a block?</h2>
<p class="ui-muted">If you want to collaborate, discuss roles, or review artifacts, reach out.</p></description></item></channel></rss>