Silicon Valley VLSI Vision Academy

We are planning to organize an online VLSI Semiconductor Career Webinar for engineering students in Bangladesh who are interested in exploring career opportunities in the semiconductor and VLSI industry.

Bangladesh has strong potential to grow in the semiconductor sector. Around the world, the demand for skilled engineers in chip design, ASIC design, RTL design, design verification, physical design, DFT, analog layout, and embedded hardware is increasing rapidly. However, many students in Bangladesh are still unaware of this field or feel confused about how to start. Due to lack of proper guidance, motivation, roadmap, and industry exposure, many talented students do not choose VLSI as a career path.

The main purpose of this webinar is to give students a clear and practical understanding of the semiconductor industry and help them see how they can build a strong career in this field from Bangladesh.
In this webinar, we will discuss:

What is VLSI and why semiconductor is important for the future
Career opportunities in chip design and semiconductor industry
Different VLSI domains such as Physical Design, RTL Design, Design Verification, DFT, Analog Layout, and ASIC Flow

How students should prepare for VLSI jobs from university level
Required technical skills, tools, projects, and interview preparation
Higher study and research opportunities in VLSI, RISC-V, hardware security, and digital design

How Bangladesh can contribute to the global semiconductor ecosystem
This session will be especially helpful for students from EEE, ECE, CSE, Electrical, Electronics, and related engineering backgrounds who are serious about building a career in VLSI and semiconductor.

I am sharing the Google registration form below. Students who are genuinely interested in this field are requested to complete the registration form. Registration is required because the webinar meeting link will be shared only with registered students through their submitted email addresses.

Registration Form: https://forms.gle/faZn6tW2yaqin3A38
Youtube Channel : https://www.youtube.com/-kw6wn
What's app 01898-757546

Silicon Valley VLSI Vision Academy Share your videos with friends, family and the world

https://youtu.be/BSUbUrIQc70?si=RXP2gvLtsnkv5_eJ

VLSI Physical Design Support Class | Industry-Level VLSI Training Are you serious about building a strong career in VLSI Physical Des...

From many students, we often receive one common question: “Why is the course price like this?” This is a very natural and valid question. Many students are new to the VLSI and Physical Design field, so they may not clearly understand what actually goes inside a professional-level training program. They may only compare the course fee with other general coaching programs, but Physical Design training is not just about attending a few lectures. It requires expensive EDA tools, proper lab access, industry-standard project flow, continuous mentor support, real debugging experience, and structured practice from basic design to higher gate-count design.

I do not want to comment on what other institutes or coaching centers are offering. Everyone has their own structure. But from our side, I want to clearly explain what we are providing, why it matters, and how this course is designed to make a student practically confident and industry-ready.

The first and most important point is tool access. In our training, each student gets 4 months of VNC support with Cadence tool access. I want to repeat this point very clearly: each student can individually use the tool. That means if 20 students are enrolled in one course, we provide 20 individual tool access environments so that every student can work independently. Students do not need to wait for someone else to finish. They do not need to share one tool window with many people. They do not need to depend on another student’s timing. Each student gets their own environment where they can run RTL-to-GDSII flow, practice commands, debug errors, modify scripts, and build confidence by doing the work themselves.

This is extremely important because Physical Design cannot be learned only by watching videos or slides. A student must run the tool personally. They must see errors, fix path issues, change TCL scripts, understand reports, analyze timing, check congestion, fix violations, and rerun the flow many times. Without individual tool access, a student may understand theory, but they will not become confident enough to work independently.

The second major opportunity is access to valuable Cadence learning materials. From Cadence training resources, there are many lecture materials, lab documents, RAKs, lab videos, command references, and practical examples. These are not ordinary public PPTs. Many of these materials are prepared with deep technical detail and professional training quality. In most cases, this type of material does not freely circulate outside. It has to be handled with proper care and confidentiality. Students who study these materials seriously can understand how each tool command works, how the flow is structured, and how professional engineers debug real design issues.

In our training, we try to give students the opportunity to learn limitlessly. We do not want students to depend only on one trainer’s class notes. We want them to see the bigger ecosystem: lecture slides, lab documents, RAK-based exercises, command usage, industry-style examples, and structured flows. These resources help them go beyond basic knowledge and understand the actual standard followed in companies.

One very important question is: when a company hires a fresher Physical Design engineer, how does the company train that engineer? From what I have seen in many semiconductor companies and service companies across India, especially in places like Bangalore, Hyderabad, Noida, Pune, Chennai, and Ahmedabad, the process is usually very structured. Companies such as Intel, Qualcomm, AMD, NVIDIA, Samsung Semiconductor, MediaTek, Texas Instruments, Synopsys, Cadence, Siemens EDA, Wipro, HCLTech, Tata Elxsi, MosChip, eInfochips, Tessolve, Mirafra, Sankalp Semiconductor and many other VLSI service companies do not directly put a fresher into complex client projects without training.
Usually, after hiring freshers, companies first train them on basic digital design, Linux, scripting, timing concepts, CMOS basics, Verilog/SystemVerilog understanding, and EDA tool flow. This initial phase may continue for one or two months. After that, they provide more focused Physical Design training for another three or four months. During that period, engineers get access to Cadence or Synopsys tools, internal design flows, RAKs, lab assignments, timing exercises, floorplanning practice, placement, CTS, routing, signoff checks, and many debugging tasks.

Companies also give practice on real or near-real designs. They may start with a small counter or simple block, then move to bigger gate-count designs such as 50K, 100K, 500K, or even 1M gate digital designs. Freshers are asked to complete timing closure, analyze setup and hold violations, check congestion, read reports, improve QoR, understand PPA, and prepare for client interviews. Along with this, they practice hundreds or thousands of interview questions so they can explain the flow confidently.

This is the professional training style used inside companies. We are trying to bring the same type of environment into our 4-month training program. Of course, we cannot claim that a course is exactly equal to working inside a company, but our goal is to give students a similar learning experience: tool access, structured projects, real commands, debugging practice, trainer support, mentor support, and confidence-building from small design to larger design.

In our training, we do not directly start with a complex design. We begin with a very simple counter design so that students can understand the basic RTL-to-GDSII flow. At the beginning, students need to learn where files are placed, how scripts are organized, how libraries are linked, how paths are set, how constraints are written, how synthesis is run, how floorplan is created, how placement and routing happen, and how reports are generated.

After students become familiar with the basic flow, we move to a mini design. This mini design helps students understand practical issues such as script modification, design path correction, library setup, constraint checking, tool error debugging, and report analysis. Students slowly start building the habit of working like real Physical Design engineers. They learn that PD is not just clicking buttons. It is a complete engineering flow where every small mistake in path, constraint, library, timing, or script can create a big error.

Once students become more confident, we move toward bigger gate-count projects. This is where they begin to experience more realistic problems. Bigger designs create more timing issues, congestion issues, placement challenges, routing problems, clock tree complexity, and signoff-related concerns. This stage is very important because industry work is not always clean and simple. A student must learn how to handle complexity, not just how to run one clean tutorial.

At the same time, we provide Cadence education materials, RAKs, lecture PPTs, lab examples, and tool command references. These materials contain many practical commands and explanations that help students solve complex tool errors. Many students get stuck because they do not know which command to use, which report to check, or which step caused the issue. The combination of live training, tool practice, RAK materials, and mentor support helps students build real problem-solving ability.

Another important point is that all students are not at the same level. Some students come from electronics background but have weak Linux knowledge. Some know Verilog but do not understand STA. Some know digital basics but have never used Cadence tools. Some are strong in theory but weak in debugging. Some are complete beginners. We understand this clearly.

That is why, at the initial stage, we provide common basic videos and supporting materials. These help students fill their knowledge gaps and come to a similar level before entering deeper Physical Design topics. We cover basic concepts that are necessary to understand the flow. Without this foundation, students may feel lost when the trainer starts talking about constraints, timing paths, libraries, floorplan, utilization, congestion, CTS, routing, setup, hold, IR drop, or signoff.

Our goal is not only to complete the syllabus. Our goal is to make each student independent. A good Physical Design engineer must be able to think, debug, analyze, and solve problems. In real industry, no one will always sit beside you and solve every issue. You must know how to read an error message, check the log file, search the report, identify whether the problem is from RTL, constraint, library, path, script, tool setup, or design quality. This independence is what we want to build.

To make someone independent, only recorded classes are not enough. Live interaction is very important. In our program, the trainer takes live classes where students can learn the concepts step by step. But we also understand that for many students, Physical Design is a completely new concept. At the beginning, they need time to catch the flow. They may not understand everything in the first class. They may need repeated explanation, doubt clearing, and practical demonstration.

That is why we arrange mentor support classes along with the regular live classes. Many times, these support sessions continue for more than three hours because we want to give full support to students. These sessions are especially useful when students face tool errors, setup problems, script issues, or flow confusion. A student may understand the class, but when they sit alone to run the tool, they may face errors. At that moment, mentor support becomes very important.

We also focus on practical confidence. A student should not only say, “I attended a Physical Design course.” The student should be able to say, “I have run RTL-to-GDSII flow myself. I have used Cadence tools. I have done synthesis, floorplanning, placement, CTS, routing, timing analysis, and report debugging. I have worked on designs from small counter to larger gate-count blocks. I have solved real tool errors. I understand the flow.”
This is the difference between a simple course and a serious training program.

When students ask about price, they should look at the full value, not only the number. They should ask:
Am I getting individual tool access?
Am I getting enough months to practice?
Am I getting live classes?
Am I getting mentor support?
Am I getting Cadence-based learning materials?
Am I getting RAK/lab-based practice?
Am I working on real projects?
Am I learning debugging?
Am I learning industry-style flow?
Am I getting preparation for interviews?
Am I becoming independent?
If the answer is yes, then the training has real value.

Physical Design is a practical field. It requires tool maturity. Many students think they can learn PD only from YouTube videos or PDF notes. Those resources are useful for basic understanding, but they cannot replace hands-on tool experience. In interviews, companies may ask theoretical questions, but they also want to know whether the candidate has practical flow knowledge. They may ask about floorplan issues, setup violation fixing, hold violation fixing, CTS problems, congestion, timing reports, clock uncertainty, false path, multicycle path, library files, LEF/DEF, SDC, SPEF, GDS, DRC/LVS, and many tool commands. Without hands-on practice, it is very difficult to answer confidently.

In our course, students get the chance to practice repeatedly. Repetition is very important in Physical Design. The first time, students may only follow the trainer. The second time, they start understanding. The third time, they start debugging. The fourth time, they gain confidence. That is why 4 months of access is important. If tool access is given only for a few days, students cannot become strong. They need enough time to practice after class, make mistakes, fix them, and rerun the flow.

We also try to build professional discipline. Students learn how to maintain design folders, how to organize scripts, how to name reports, how to compare QoR, how to document issues, and how to explain their work. These are small but important habits. In industry, clean work matters. A PD engineer must be able to explain what they changed, why they changed it, and what impact it had on timing, area, power, congestion, or routing.

Another important value is exposure to interview-level thinking. We try to connect every practical step with interview questions. For example, when students do floorplanning, we discuss why utilization matters, why macro placement matters, why power planning is important, and how congestion can start from a bad floorplan. When students do CTS, we discuss skew, latency, clock buffers, useful skew, and clock uncertainty. When students do timing, we explain setup and hold violations with real report interpretation. This way, students do not memorize answers blindly. They understand the reason behind each answer.

Our training is designed for serious learners who want to enter the VLSI industry with confidence. We know that every student may not become perfect in 4 months, but with proper effort, they can build a strong foundation and practical confidence. The student must also work hard. Tool access and training are opportunities, but the student has to use them. If a student regularly attends class, practices on VNC, studies the material, asks questions, and completes assignments, they will improve significantly.

So, when we talk about course price, we are not charging only for lectures. We are providing a complete learning ecosystem:
4 months of individual VNC-based Cadence tool access
Live classes by trainer
Mentor support and doubt clearing
Basic foundation videos
Hands-on RTL-to-GDSII flow
Small design to bigger gate-count project practice
Cadence lecture materials and RAK-based learning
Lab videos and tool command exposure
Script modification and debugging practice
Timing, placement, CTS, routing, and signoff understanding
Interview-oriented explanation
Industry-style learning process
This is why the course has value.

Our final goal is simple: we want students to become independent Physical Design learners and future engineers. We want them to understand the tool, the flow, the reports, the errors, and the logic behind each step. We want them to move from fear to confidence. At the beginning, many students feel Physical Design is very complex. But with proper guidance, continuous tool practice, and strong support, they slowly understand the flow and start solving problems independently.
That is the real purpose of this training.

We are not only teaching commands. We are trying to create an environment similar to how freshers are trained in professional semiconductor companies. We are giving students access, materials, projects, support, and practical exposure so that they can prepare themselves for the real VLSI industry.
For any student who is serious about Physical Design, the most important investment is not only money. It is time, practice, discipline, and the right environment. Our course is built to provide that environment.







of Science & Technology Chittagong





#𝘼𝙄𝙐𝘽




University of Asia Pacific - UAP
Independent University, Bangladesh
International Islamic University Chittagong
BUET - Bangladesh University of Engineering and Technology
Khulna University of Engineering & Technology - KUET
Rajshahi University of Engineering and Technology - RUET
RUET
Chittagong University of Engineering & Technology - CUET
North South University
University of Science and Technology Chittagong- USTC
Central Women's University
IUBAT—International University of Business Agriculture and Technology
Ahsanullah University of Science & Technology (AUST)
Ahsanullah University of Science & Technology
American International University-Bangladesh
East West University
University of Asia Pacific - UAP
Asian University of Bangladesh - AUB
Dhaka International University - DIU
Manarat International University
BRAC University
Sylhet International University
Premier University, Chittagong
Daffodil International University
Northern University Bangladesh
Uttara University
United International University
University of South Asia
United International University
Bangladesh University of Business and Technology - BUBT

Many students today make one big mistake: they try to jump directly to ChatGPT or AI tools without building their own foundation first.

ChatGPT, Copilot, Claude, and other AI tools are very powerful, but they are not a replacement for learning. They can help you write code, explain concepts, debug errors, and improve productivity, but only when you already understand the basics.

In VLSI, especially RTL Design and Verification, you cannot skip the core path:

Digital Logic Fundamentals → Verilog/SystemVerilog → Computer Architecture → RTL Design → Timing & CDC Basics → Verification Fundamentals → UVM → Debugging → Formal Verification → AI Tools → System-Level Thinking

The problem is, many students start from the top step instead of the bottom step. They ask ChatGPT for RTL code, UVM testbench, assertions, or synthesis fixes, but they do not understand why the code works, where the bug is, or whether the answer is technically correct.

That becomes dangerous in real projects.

Because in industry, nobody pays you only to copy code. You are expected to understand the design, find bugs, debug waveform issues, analyze timing, understand protocol behavior, and explain your solution clearly.

AI can make a skilled engineer faster.
But AI cannot make a weak foundation strong overnight.

So the right approach is:

First learn the concept.
Then write code by yourself.
Then debug your own mistakes.
Then use ChatGPT as a support tool to improve, verify, and speed up your work.

Do not use AI as a shortcut.
Use AI as an accelerator after building your own skill.

Foundation first. AI second. Skill always matters.

🚀 𝐀𝐝𝐯𝐚𝐧𝐜𝐞𝐝 𝐕𝐋𝐒𝐈 𝐏𝐡𝐲𝐬𝐢𝐜𝐚𝐥 𝐃𝐞𝐬𝐢𝐠𝐧 𝐂𝐨𝐮𝐫𝐬𝐞 | 𝐅𝐫𝐨𝐦 𝐑𝐓𝐋 𝐭𝐨 𝐆𝐃𝐒𝐈𝐈 𝐰𝐢𝐭𝐡 𝐑𝐞𝐚𝐥 𝐈𝐧𝐝𝐮𝐬𝐭𝐫𝐲 𝐅𝐥𝐨𝐰

Physical Design is not about memorizing commands — it is about building real silicon.

In the VLSI industry, companies do not hire only based on certificates. They look for engineers who can work on real tools, debug real design issues, and handle silicon-level challenges.

That is why our Advanced Physical Design Course is designed to give students a true industry-like learning environment with hands-on project exposure, real Cadence tools, and complete RTL to GDSII implementation flow.

🔥 𝐖𝐡𝐲 𝐓𝐡𝐢𝐬 𝐏𝐡𝐲𝐬𝐢𝐜𝐚𝐥 𝐃𝐞𝐬𝐢𝐠𝐧 𝐂𝐨𝐮𝐫𝐬𝐞 𝐈𝐬 𝐃𝐢𝐟𝐟𝐞𝐫𝐞𝐧t

✅ 𝐈𝐧𝐝𝐮𝐬𝐭𝐫𝐲-𝐃𝐫𝐢𝐯𝐞𝐧 𝐂𝐨𝐮𝐫𝐬𝐞 𝐎𝐮𝐭𝐥𝐢𝐧𝐞
No outdated academic-only syllabus. Our course is designed based on current semiconductor industry expectations, interview needs, and real project challenges.

✅ 𝐒𝐞𝐩𝐚𝐫𝐚𝐭𝐞 𝟐𝟒×𝟕 𝐂𝐚𝐝𝐞𝐧𝐜𝐞 𝐒𝐞𝐫𝐯𝐞𝐫 𝐀𝐜𝐜𝐞𝐬𝐬
Every student gets individual Cadence server access through VNC, similar to a real company setup.
No shared login. No fixed lab timing. Practice anytime, repeat labs, and debug independently.

✅ 𝐂𝐚𝐝𝐞𝐧𝐜𝐞 𝐄𝐝𝐮𝐜𝐚𝐭𝐢𝐨𝐧 𝐋𝐢𝐜𝐞𝐧𝐬𝐞𝐝 𝐓𝐨𝐨𝐥𝐬
Students work on official Cadence Education tools, not cracked or demo software. This helps them understand real tool behavior, commands, errors, reports, and industry-style ex*****on.

✅ 𝐂𝐨𝐦𝐩𝐥𝐞𝐭𝐞 𝐑𝐓𝐋 𝐭𝐨 𝐆𝐃𝐒𝐈𝐈 𝐄𝐧𝐝-𝐭𝐨-𝐄𝐧𝐝 𝐅𝐥𝐨𝐰
Students will learn the full Physical Design flow:

1️⃣ Floorplanning
2️⃣ Power Planning
3️⃣ Placement
4️⃣ Optimization
5️⃣ Clock Tree Synthesis
6️⃣ Routing
7️⃣ Timing Closure
8️⃣ DRC & LVS Concepts
9️⃣ Final GDSII Flow Understanding

✅ 𝐇𝐢𝐠𝐡-𝐂𝐨𝐦𝐩𝐥𝐞𝐱𝐢𝐭𝐲 𝐏𝐫𝐨𝐣𝐞𝐜𝐭 𝐄𝐱𝐩𝐨𝐬𝐮𝐫𝐞
Students will work on a 550K+ instance complex design, not a toy example. This gives real exposure to congestion, timing violations, optimization issues, power-area tradeoffs, and debugging techniques.

✅ 𝐇𝐚𝐧𝐝𝐬-𝐎𝐧 𝐅𝐨𝐜𝐮𝐬𝐞𝐝 𝐋𝐞𝐚𝐫𝐧𝐢𝐧𝐠
Physical Design cannot be mastered by watching videos only.
In this course, students will practice more, debug more, and understand why each step is done in the PD flow.

✅ 𝐉𝐨𝐛-𝐎𝐫𝐢𝐞𝐧𝐭𝐞𝐝 & 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰-𝐑𝐞𝐚𝐝𝐲 𝐓𝐫𝐚𝐢𝐧𝐢𝐧𝐠
By the end of the course, students will be able to confidently explain:

✔️ Complete Physical Design flow
✔️ Floorplan strategy
✔️ Timing closure challenges
✔️ Congestion and routing issues
✔️ CTS and optimization concepts
✔️ Real project debugging approach

This course is not for those looking for shortcuts or theory-only learning.
This course is for serious learners who want to become industry-ready Physical Design Engineers.

𝐎𝐮𝐫 𝐠𝐨𝐚𝐥 𝐢𝐬 𝐯𝐞𝐫𝐲 𝐜𝐥𝐞𝐚𝐫:

We want to build independent VLSI engineers who can think, debug, analyze, and solve real design problems without depending on memorized commands.

🔹 𝐅𝐫𝐨𝐦 𝐁𝐚𝐬𝐢𝐜 𝐂𝐨𝐮𝐧𝐭𝐞𝐫 𝐭𝐨 𝐑𝐞𝐚𝐥 𝐃𝐞𝐬𝐢𝐠𝐧 𝐅𝐥𝐨𝐰:
Students first start with a simple counter design to understand synthesis flow, tool behavior, reports, constraints, and basic debugging.

🔹 𝐑𝐞𝐚𝐥 𝐃𝐞𝐛𝐮𝐠𝐠𝐢𝐧𝐠 𝐓𝐡𝐫𝐨𝐮𝐠𝐡 𝟖-𝐛𝐢𝐭 𝐒𝐞𝐫𝐃𝐞𝐬 𝐏𝐫𝐨𝐣𝐞𝐜𝐭
After that, students move to a high-speed 8-bit Serializer/Deserializer project, where they face real issues like synthesis errors, wrong constraints, timing failures, script problems, and low-power synthesis challenges.

🔹 𝐍𝐨 𝐑𝐞𝐚𝐝𝐲-𝐌𝐚𝐝𝐞 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧 — 𝐖𝐞 𝐓𝐫𝐚𝐢𝐧 𝐒𝐭𝐮𝐝𝐞𝐧𝐭𝐬 𝐭𝐨 𝐓𝐡𝐢𝐧𝐤
We don’t simply give answers.
We guide students to find the root cause, understand why the error happened, and fix it like a real engineer.

🔹 𝟑+ 𝐇𝐨𝐮𝐫𝐬 𝐄𝐱𝐭𝐞𝐧𝐝𝐞𝐝 𝐌𝐞𝐧𝐭𝐨𝐫 𝐒𝐮𝐩𝐩𝐨𝐫𝐭 𝐂𝐥𝐚𝐬𝐬𝐞𝐬
After regular sessions, our mentor team provides long support classes where every student’s problem is discussed and solved step by step.

No student is left behind.

🔹 𝐑𝐞𝐚𝐥 𝐂𝐥𝐢𝐞𝐧𝐭-𝐋𝐞𝐯𝐞𝐥 𝐌𝐮𝐥𝐭𝐢-𝐂𝐨𝐫𝐞 𝐓𝐢𝐧𝐲 𝐆𝐏𝐔 𝐏𝐫𝐨𝐣𝐞𝐜𝐭
Once students gain confidence, they work on a Multi-Core Tiny GPU Architecture synthesis project, where they are encouraged to work independently.

This is where real engineering confidence starts.

🔹 𝐂𝐚𝐝𝐞𝐧𝐜𝐞 𝟒𝟓𝐧𝐦 & 𝟕𝐧𝐦 𝐏𝐃𝐊 𝐄𝐱𝐩𝐨𝐬𝐮𝐫𝐞
Students work with both 45nm and 7nm PDKs to understand real differences in timing, area, power, slack, QoR, and optimization behavior.

🔹 𝐈𝐧𝐝𝐮𝐬𝐭𝐫𝐲-𝐋𝐞𝐯𝐞𝐥 𝐓𝐢𝐦𝐢𝐧𝐠 & 𝐐𝐨𝐑 𝐔𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝𝐢𝐧𝐠
Students learn how to analyze setup/hold violations, critical paths, pipeline delays, slack issues, power optimization, and area improvement.

They also understand why 0 ps slack is risky, even when timing looks passed.

🔹 𝐑𝐞𝐬𝐩𝐞𝐜𝐭 𝐭𝐨 𝐎𝐮𝐫 𝐒𝐭𝐮𝐝𝐞𝐧𝐭𝐬
We truly appreciate our students who are managing university classes, exams, quizzes, assignments, and this intensive VLSI training together.

Their dedication shows their real passion for becoming Physical Design Engineers.

🎯 𝐎𝐮𝐫 𝐅𝐢𝐧𝐚𝐥 𝐌𝐢𝐬𝐬𝐢𝐨𝐧

We don’t just teach tools.
We build engineers who can think independently, debug confidently, analyze reports, and solve real Physical Design problems.

📩 𝐒𝐞𝐚𝐭𝐬 𝐚𝐫𝐞 𝐥𝐢𝐦𝐢𝐭𝐞𝐝 𝐛𝐞𝐜𝐚𝐮𝐬𝐞 𝐰𝐞 𝐟𝐨𝐜𝐮𝐬 𝐨𝐧 𝐪𝐮𝐚𝐥𝐢𝐭𝐲 𝐡𝐚𝐧𝐝𝐬-𝐨𝐧 𝐭𝐫𝐚𝐢𝐧𝐢𝐧𝐠, 𝐧𝐨𝐭 𝐦𝐚𝐬𝐬 𝐞𝐧𝐫𝐨𝐥𝐥𝐦𝐞𝐧𝐭.

If you are serious about building your career in VLSI Physical Design, this is the right time to start.

Don’t just learn commands — learn how real Physical Design engineers work on real silicon projects.

👉 𝐃𝐌 𝐮𝐬 𝐧𝐨𝐰 𝐰𝐢𝐭𝐡 “𝐏𝐃 𝐂𝐎𝐔𝐑𝐒𝐄” 𝐭𝐨 𝐠𝐞𝐭 𝐭𝐡𝐞 𝐟𝐮𝐥𝐥 𝐜𝐨𝐮𝐫𝐬𝐞 𝐝𝐞𝐭𝐚𝐢𝐥𝐬, 𝐬𝐲𝐥𝐥𝐚𝐛𝐮𝐬, 𝐟𝐞𝐞 𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞, 𝐚𝐧𝐝 𝐞𝐧𝐫𝐨𝐥𝐥𝐦𝐞𝐧𝐭 𝐩𝐫𝐨𝐜𝐞𝐬𝐬.

🚀 𝐒𝐭𝐚𝐫𝐭 𝐲𝐨𝐮𝐫 𝐣𝐨𝐮𝐫𝐧𝐞𝐲 𝐟𝐫𝐨𝐦 𝐥𝐞𝐚𝐫𝐧𝐞𝐫 𝐭𝐨 𝐢𝐧𝐝𝐮𝐬𝐭𝐫𝐲-𝐫𝐞𝐚𝐝𝐲 𝐏𝐡𝐲𝐬𝐢𝐜𝐚𝐥 𝐃𝐞𝐬𝐢𝐠𝐧 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫.

📩 For details & registration:
📞 WhatsApp: +8801898757546

𝐏𝐡𝐨𝐭𝐨/𝐢𝐦𝐚𝐠𝐞 𝐜𝐫𝐞𝐝𝐢𝐭:
𝐭𝐡𝐢𝐬 𝐟𝐮𝐥𝐥 𝐢𝐦𝐚𝐠𝐞 𝐜𝐫𝐞𝐝𝐢𝐭 𝐠𝐨𝐞𝐬 𝐭𝐨 𝐨𝐧𝐞 𝐨𝐟 𝐨𝐮𝐫 𝐭𝐨𝐩-𝐩𝐞𝐫𝐟𝐨𝐫𝐦𝐢𝐧𝐠 𝐚𝐧𝐝 𝐡𝐚𝐫𝐝𝐰𝐨𝐫𝐤𝐢𝐧𝐠 𝐬𝐭𝐮𝐝𝐞𝐧𝐭𝐬, 𝐰𝐡𝐨𝐬𝐞 𝐝𝐞𝐝𝐢𝐜𝐚𝐭𝐢𝐨𝐧, 𝐜𝐨𝐧𝐭𝐢𝐧𝐮𝐨𝐮𝐬 𝐩𝐫𝐚𝐜𝐭𝐢𝐜𝐞, 𝐚𝐧𝐝 𝐩𝐫𝐨𝐛𝐥𝐞𝐦-𝐬𝐨𝐥𝐯𝐢𝐧𝐠 𝐦𝐢𝐧𝐝𝐬𝐞𝐭 𝐭𝐫𝐮𝐥𝐲 𝐫𝐞𝐟𝐥𝐞𝐜𝐭 𝐭𝐡𝐞 𝐬𝐩𝐢𝐫𝐢𝐭 𝐨𝐟 𝐛𝐞𝐜𝐨𝐦𝐢𝐧𝐠 𝐚𝐧 𝐢𝐧𝐝𝐮𝐬𝐭𝐫𝐲-𝐫𝐞𝐚𝐝𝐲 𝐩𝐡𝐲𝐬𝐢𝐜𝐚𝐥 𝐝𝐞𝐬𝐢𝐠𝐧 𝐞𝐧𝐠𝐢𝐧𝐞𝐞𝐫.

















United International University
Bangladesh University of Business and Technology - BUBT
Independent University, Bangladesh
International Islamic University Chittagong
BUET - Bangladesh University of Engineering and Technology
Khulna University of Engineering & Technology - KUET
North South University
Chittagong University of Engineering & Technology(CUET)
Ahsanullah University of Science and Technology
American International University-Bangladesh
North South University
University of Asia Pacific - UAP
Dhaka International University - DIU

A processor does not execute instructions randomly. It follows a fixed step-by-step process called the instruction cycle. In LC-3, this cycle is controlled by a Finite State Machine (FSM). The FSM decides which operation will happen first, which register will be loaded, when memory will be accessed, and where the processor should go next.

𝐖𝐡𝐚𝐭 𝐭𝐡𝐞 𝐅𝐒𝐌 𝐃𝐨𝐞𝐬?

The FSM works like the controller or brain of the processor. It sends control signals at the correct time. For example, it tells the PC to put its value on the bus, tells MAR to store that address, tells memory to read data, and tells IR to store the fetched instruction. Without the FSM, the processor would not know the correct order of operations.

𝐒𝐭𝐚𝐭𝐞 𝟏: 𝐒𝐭𝐚𝐫𝐭 𝐨𝐟 𝐅𝐞𝐭𝐜𝐡

In the first state, the processor starts fetching the next instruction. The address stored in the PC, or Program Counter, is copied into MAR, the Memory Address Register. This tells memory which address to read. At the same time, the PC is increased so it points to the next instruction. In simple words, the CPU says: “Go to this memory address and prepare for the next instruction.”

𝐒𝐭𝐚𝐭𝐞 𝟐: 𝐌𝐞𝐦𝐨𝐫𝐲 𝐀𝐜𝐜𝐞𝐬𝐬

In the second state, memory is accessed using the address stored in MAR. The instruction stored at that memory location is read and placed into MDR, the Memory Data Register. MDR temporarily holds the instruction that comes from memory.

𝐒𝐭𝐚𝐭𝐞 𝟑: 𝐋𝐨𝐚𝐝 𝐈𝐧𝐬𝐭𝐫𝐮𝐜𝐭𝐢𝐨𝐧 𝐑𝐞𝐠𝐢𝐬𝐭𝐞𝐫

In the third state, the instruction inside MDR is copied into IR, the Instruction Register. Now the instruction is officially inside the processor. After this step, the processor can understand what operation it needs to perform.

𝐒𝐭𝐚𝐭𝐞 𝟒: 𝐃𝐞𝐜𝐨𝐝𝐞

In the fourth state, the processor decodes the instruction. It checks the opcode to understand what type of instruction it is. The instruction could be ADD, LDR, JMP, or another operation. Based on the opcode, the FSM chooses the correct ex*****on path.

𝐃𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐭 𝐈𝐧𝐬𝐭𝐫𝐮𝐜𝐭𝐢𝐨𝐧𝐬 𝐓𝐚𝐤𝐞 𝐃𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐭 𝐏𝐚𝐭𝐡𝐬

After decode, every instruction does not follow the same path. An ADD instruction goes to ALU-related states. An LDR instruction goes through address calculation and memory access states. A JMP instruction updates the PC with a register value. So the FSM branches into different paths depending on the instruction type.

𝐄𝐱𝐚𝐦𝐩𝐥𝐞: 𝐀𝐃𝐃 𝐈𝐧𝐬𝐭𝐫𝐮𝐜𝐭𝐢𝐨𝐧

For an ADD instruction, the processor reads the required registers, performs addition using the ALU, stores the result back into the destination register, and then returns to State 1 to fetch the next instruction.

𝐄𝐱𝐚𝐦𝐩𝐥𝐞: 𝐋𝐃𝐑 𝐈𝐧𝐬𝐭𝐫𝐮𝐜𝐭𝐢𝐨𝐧

For an LDR instruction, the processor calculates the memory address, accesses memory, loads the data, writes it into the destination register, and then returns to State 1. This type of instruction takes more steps because memory access is involved.

𝐄𝐱𝐚𝐦𝐩𝐥𝐞: 𝐉𝐌𝐏 𝐈𝐧𝐬𝐭𝐫𝐮𝐜𝐭𝐢𝐨𝐧

For a JMP instruction, the processor changes the PC using a register value. This means the next instruction will not come from the normal next address. Instead, the CPU jumps to a new address. After updating the PC, the FSM returns to State 1.

𝐖𝐡𝐲 𝐈𝐭 𝐀𝐥𝐰𝐚𝐲𝐬 𝐑𝐞𝐭𝐮𝐫𝐧𝐬 𝐭𝐨 𝐒𝐭𝐚𝐭𝐞 𝟏

After every instruction finishes, the processor must fetch the next instruction. That is why all ex*****on paths eventually return to State 1. This creates the repeated cycle: fetch, decode, execute, and fetch again.

The LC-3 instruction cycle is controlled by an FSM. First, the CPU fetches the instruction from memory. Then it loads the instruction into IR. After that, it decodes the opcode and chooses the correct ex*****on path. Once the instruction is complete, the processor returns to the fetch state and starts the next instruction.