Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Most C Programmers don't have a clue as to how the CPU works. Here is a lecture from my course on the C Language that introduces how to visualise the CPU as a C (or general software) Programmer.... More Details are at: Being able to model the behaviour of... show more

Piyush Itankar

7,996 subscribers

28,019 views • 1 year ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

7 Comments

Piyush Itankar1 year ago

Added three more lectures to the course today.

SecurityPal2 years ago

Discover how a culture of learning and mentorship can shape the future of cybersecurity. In this episode of ‘In Security’ podcast, Ryan Black, CISO at @BlackCloakCyber, discusses the importance of practical tools like the Capture The Flag framework. 🔗:

David Pfohmann1 year ago

How do you know that most C programmers don't know how the CPU works?

Piyush Itankar1 year ago

Have interacted with many C programmers over the past decade and very few could reason about the CPU. What I should have said is “most C programmers I interacted with…”, rather than saying “most C programmers…” Should have made it specific. What’s your opinion?

katzz1 year ago

Great explanation 🫡🫡🫡👏👏

ᗰṳhumuzå ₱ɨuṩ1 year ago

Thank you for this visualization Piyush. It's very insightful

Eduardo Bergel1 year ago

🔖🔖🔖

Related Videos

C Language is to be learnt by running experiments on Bare-metal (just the CPU) and without the OS noise! I added more lectures to the C Language course under the "Bitwise Operators" and the video (a snippet from the last lecture listed above) shows the level to which the course is hands-on. I pretty much prove all the claims I make about the concepts by experiments! Lectures I added include - + What are bitwise operations and the types + Shift Operations - Left, Logical and Arithmetic Right + The Bitwise NOT operation + Understanding using printf + Understanding the Assembly View + Exploring the Shift operations + Assembly view of Shift operation I have been recording this course for over a year now, 91 Lectures (almost all with hands on experiments) and we are far from concluding it. I'll continue to add more... If learning by experimenting (and reasoning from first principles) is your thing, you will love this course. This is included as part of the library access and you can check the current table on contents here:

C Language is to be learnt by running experiments on Bare-metal (just the CPU) and without the OS noise! I added more lectures to the C Language course under the "Bitwise Operators" and the video (a snippet from the last lecture listed above) shows the level to which the course is hands-on. I pretty much prove all the claims I make about the concepts by experiments! Lectures I added include - + What are bitwise operations and the types + Shift Operations - Left, Logical and Arithmetic Right + The Bitwise NOT operation + Understanding using printf + Understanding the Assembly View + Exploring the Shift operations + Assembly view of Shift operation I have been recording this course for over a year now, 91 Lectures (almost all with hands on experiments) and we are far from concluding it. I'll continue to add more... If learning by experimenting (and reasoning from first principles) is your thing, you will love this course. This is included as part of the library access and you can check the current table on contents here:

Piyush Itankar

41,636 views • 6 months ago

the new --cpu-prof flag is a really nice way to see how much of your time Bun is spending on the CPU ⚡ you can open the profile directly in VSCode/Cursor/Chrome DevTools. also makes it easier to compare how your script performs in Bun vs Node!

Lydia Hallie ✨

70,061 views • 8 months ago

A year ago I made a video about the RIDL CPU vulnerability. In case you haven't seen it, here it is uploaded to Twitter directly! The most interesting part of this has been learning about the prior research that later lead to the discovery of these modern side-channel vulnerabilities. I also spend more time explaining "speculative execution" and how these CPU cache timings can be used as a side-channel. If you haven't seen it yet, give it another chance :)

A year ago I made a video about the RIDL CPU vulnerability. In case you haven't seen it, here it is uploaded to Twitter directly! The most interesting part of this has been learning about the prior research that later lead to the discovery of these modern side-channel vulnerabilities. I also spend more time explaining "speculative execution" and how these CPU cache timings can be used as a side-channel. If you haven't seen it yet, give it another chance :)

LiveOverflow 🔴

18,151 views • 2 years ago

The next generation of mobile experiences is here. #Snapdragon 8 Elite features the fastest mobile CPU in the world thanks to the Qualcomm Oryon CPU, paired with the most powerful on-device #AI ever for a smartphone.

The next generation of mobile experiences is here. #Snapdragon 8 Elite features the fastest mobile CPU in the world thanks to the Qualcomm Oryon CPU, paired with the most powerful on-device #AI ever for a smartphone.

Snapdragon

30,459 views • 1 year ago

** Sega Genesis 3D Engine Day 3 ** Blast Processing kicks In !! Converted the Line Drawing and Triangle drawing to 68k Assembly and gained 25% in the line drawing and 33% speedups in the triangle drawing vs C ( so far ) . The scheduler calculating the vertexs is still in C , just the drawing routines are now are in assembly . Possibly 5-10 % gains will come from the scheduler being in ASM also. The Line and Triangle drawing C code took some beating , it was surprising - particularly the line drawing to get a speed up over the C code in ASM. I guess its not too surprising as the C code was basically handling pointers and integers so I had to get exotic to find the speedups. Initially my ASM Line draw was 100% slower than the C code - the first pass conversion from C to ASM is always rough as its more about getting it working then refine later , but yeah 100% slower on first pass was brutal, after 4 hrs tweaking it was 25% faster than the C code so thats a good start - might get more yet. So added more squares and more triangles for load testing at the same frame rate. Its still not anything cohesive but right now focussing on performance in rendering to see how much can be pushed. As rendering will be the biggest cpu soak the faster that goes the better. The smaller triangles take about 1/3 the CPU time of the larger triangles at present so theres definately a fill rate limit vs the setup time to consider. The same would go for the squares been line framed - smaller ones would allow al lot more . #SGDK #SegaGenesis #SegaMegadrive

Sega Genesis 3D Engine Day 3 Blast Processing kicks In !! Converted the Line Drawing and Triangle drawing to 68k Assembly and gained 25% in the line drawing and 33% speedups in the triangle drawing vs C ( so far ) . The scheduler calculating the vertexs is still in C , just the drawing routines are now are in assembly . Possibly 5-10 % gains will come from the scheduler being in ASM also. The Line and Triangle drawing C code took some beating , it was surprising - particularly the line drawing to get a speed up over the C code in ASM. I guess its not too surprising as the C code was basically handling pointers and integers so I had to get exotic to find the speedups. Initially my ASM Line draw was 100% slower than the C code - the first pass conversion from C to ASM is always rough as its more about getting it working then refine later , but yeah 100% slower on first pass was brutal, after 4 hrs tweaking it was 25% faster than the C code so thats a good start - might get more yet. So added more squares and more triangles for load testing at the same frame rate. Its still not anything cohesive but right now focussing on performance in rendering to see how much can be pushed. As rendering will be the biggest cpu soak the faster that goes the better. The smaller triangles take about 1/3 the CPU time of the larger triangles at present so theres definately a fill rate limit vs the setup time to consider. The same would go for the squares been line framed - smaller ones would allow al lot more . #SGDK #SegaGenesis #SegaMegadrive

Shannon Birt

21,171 views • 3 months ago

Xbox Series S is able to run Starfield at 120fps with a mod(yes 120fps), and 60 to 70fps in New Atlantis. 👍 "But but the Series S is a potato 🥔" Nah the potatoes 🥔 are the lazy devs. The cpu on Series S is stronger than the cpu on the PS5. #XboxSeriesS #Starfield #120FPS

Xbox Series S is able to run Starfield at 120fps with a mod(yes 120fps), and 60 to 70fps in New Atlantis. 👍 "But but the Series S is a potato 🥔" Nah the potatoes 🥔 are the lazy devs. The cpu on Series S is stronger than the cpu on the PS5. #XboxSeriesS #Starfield #120FPS

✖️Astal✖️

623,183 views • 2 years ago

Jensen Huang just identified the next $200 billion market (Save this). The shift starts with a observation about agentic AI that changes everything about infrastructure. In the era of training and inference, the GPU was everything while CPU was a traffic cop, scheduling work, managing memory, dispatching tasks while the GPU did the heavy lifting. Agentic AI breaks that model entirely. An AI agent does not just run a single inference pass but rather it plans, calls tools, executes code in sandboxes, retrieves data from multiple sources and loops through complex multi-step reasoning sequences often thousands of times per second at scale. Every one of those operations runs through the CPU and the GPU sits idle waiting for the CPU to prepare the next task, supply the right context and execute the retrieval and tool calling logic fast enough to keep the accelerators fed. The CPU is now the conductor and the GPU is the orchestra and the bottleneck is the conductor falling behind. This is showing up in production AI factory utilization right now, which is exactly why Jensen built Vera from scratch rather than licensing x86. Vera achieves 40% lower peak memory latency than x86, 50% faster core to core communication, and 1.8 times the agentic sandbox performance of current x86 processors on a purpose-built architecture designed around the agentic loop. Now here is where the investment thesis gets interesting. The obvious beneficiary is Nvidia itself, and that thesis is real. Nvidia's CFO has guided for nearly $20 billion in Vera CPU revenue this fiscal year alone, a market Nvidia had zero presence in just three years ago. Intel held 60% of server CPU market share as recently as Q4 2025 and that transition is now happening at a pace Intel structurally cannot respond to. But the deeper question is, what architecture is Vera actually built on? Vera's Olympus cores are ARM compatible and every single Vera CPU deployed in every Vera Rubin rack in every data center in the world runs on ARM architecture. And ARM Holdings collects a royalty on every one of them. ARM does not make chips but rather licenses the instruction set architecture and CPU core designs that others build on top of. Every time Nvidia ships a Vera CPU, every time a hyperscaler deploys a Vera Rubin rack, every time an enterprise qualifies Vera for their AI factory, ARM earns a royalty. The secular tailwind here is almost perfectly constructed for ARM's business model. Amazon's Graviton, Microsoft's Cobalt, Google's Axion, Apple's silicon stack, and Qualcomm's data center push all run on ARM. And now Nvidia's Vera, which is projected to displace Intel as the largest server CPU supplier by revenue in a single fiscal year, is ARM. ARM's royalty rate on high end server chips is estimated at roughly 1 to 2% of chip selling price. At $5,000 per Vera CPU and 4 million units projected for FY2027, that is a royalty line growing from near zero to potentially $400 million to $800 million annually from Nvidia's data center CPU business alone before counting Amazon, Microsoft, Google, Apple, and Qualcomm. The total ARM addressable royalty base across all the silicon it already licenses is compounding at a rate that the current $130 billion market cap does not fully reflect. Jensen's CPU thesis is the most underappreciated catalyst in ARM's fundamental story, and the royalty compounding has barely started. Come join Milk Road Pro and get our full ARM royalty model and our entire AI trade thesis. Link below!

Jensen Huang just identified the next $200 billion market (Save this). The shift starts with a observation about agentic AI that changes everything about infrastructure. In the era of training and inference, the GPU was everything while CPU was a traffic cop, scheduling work, managing memory, dispatching tasks while the GPU did the heavy lifting. Agentic AI breaks that model entirely. An AI agent does not just run a single inference pass but rather it plans, calls tools, executes code in sandboxes, retrieves data from multiple sources and loops through complex multi-step reasoning sequences often thousands of times per second at scale. Every one of those operations runs through the CPU and the GPU sits idle waiting for the CPU to prepare the next task, supply the right context and execute the retrieval and tool calling logic fast enough to keep the accelerators fed. The CPU is now the conductor and the GPU is the orchestra and the bottleneck is the conductor falling behind. This is showing up in production AI factory utilization right now, which is exactly why Jensen built Vera from scratch rather than licensing x86. Vera achieves 40% lower peak memory latency than x86, 50% faster core to core communication, and 1.8 times the agentic sandbox performance of current x86 processors on a purpose-built architecture designed around the agentic loop. Now here is where the investment thesis gets interesting. The obvious beneficiary is Nvidia itself, and that thesis is real. Nvidia's CFO has guided for nearly $20 billion in Vera CPU revenue this fiscal year alone, a market Nvidia had zero presence in just three years ago. Intel held 60% of server CPU market share as recently as Q4 2025 and that transition is now happening at a pace Intel structurally cannot respond to. But the deeper question is, what architecture is Vera actually built on? Vera's Olympus cores are ARM compatible and every single Vera CPU deployed in every Vera Rubin rack in every data center in the world runs on ARM architecture. And ARM Holdings collects a royalty on every one of them. ARM does not make chips but rather licenses the instruction set architecture and CPU core designs that others build on top of. Every time Nvidia ships a Vera CPU, every time a hyperscaler deploys a Vera Rubin rack, every time an enterprise qualifies Vera for their AI factory, ARM earns a royalty. The secular tailwind here is almost perfectly constructed for ARM's business model. Amazon's Graviton, Microsoft's Cobalt, Google's Axion, Apple's silicon stack, and Qualcomm's data center push all run on ARM. And now Nvidia's Vera, which is projected to displace Intel as the largest server CPU supplier by revenue in a single fiscal year, is ARM. ARM's royalty rate on high end server chips is estimated at roughly 1 to 2% of chip selling price. At $5,000 per Vera CPU and 4 million units projected for FY2027, that is a royalty line growing from near zero to potentially $400 million to $800 million annually from Nvidia's data center CPU business alone before counting Amazon, Microsoft, Google, Apple, and Qualcomm. The total ARM addressable royalty base across all the silicon it already licenses is compounding at a rate that the current $130 billion market cap does not fully reflect. Jensen's CPU thesis is the most underappreciated catalyst in ARM's fundamental story, and the royalty compounding has barely started. Come join Milk Road Pro and get our full ARM royalty model and our entire AI trade thesis. Link below!

Milk Road AI

11,819 views • 2 months ago

Every year I use ZERO "Run plays" for the CPU in #NBA2K26 and a lot of people ask why. People think it causes the CPU to never run plays, but as you can see if you can balance the individual player tendencies correctly the result is a smooth authentic CPU offensive experience.

Every year I use ZERO "Run plays" for the CPU in #NBA2K26 and a lot of people ask why. People think it causes the CPU to never run plays, but as you can see if you can balance the individual player tendencies correctly the result is a smooth authentic CPU offensive experience.

Shady 🧊

184,692 views • 4 months ago

Monad Testnet Visualized (Pt 3) I think Claude and I have fixed the freeze/pause issue. Works a lot smoother and most of the jitter is now just due to my GPU/CPU begging for mercy trying to handle the data visualization

Monad Testnet Visualized (Pt 3) I think Claude and I have fixed the freeze/pause issue. Works a lot smoother and most of the jitter is now just due to my GPU/CPU begging for mercy trying to handle the data visualization

Ray J

18,673 views • 1 year ago

AMD CEO LISA SU JUST DOUBLED HER OWN CPU FORECAST IN 6 MONTHS In November, she told investors the CPU market would grow 18-20% per year through 2030. This morning she revised that number: "That rate is doubling. The CPU market may be over $120 billion by 2030, growing at over 35%." The driver: agents. Six months ago AMD modeled 1 CPU for every 4 to 8 GPUs in an AI data center. The new ratio is closer to 1 to 1. Su on CNBC: "Each of us could have 2 or 3 or even 5 or 10 agents doing work on our behalf. That means you need a lot more CPU compute."

AMD CEO LISA SU JUST DOUBLED HER OWN CPU FORECAST IN 6 MONTHS In November, she told investors the CPU market would grow 18-20% per year through 2030. This morning she revised that number: "That rate is doubling. The CPU market may be over $120 billion by 2030, growing at over 35%." The driver: agents. Six months ago AMD modeled 1 CPU for every 4 to 8 GPUs in an AI data center. The new ratio is closer to 1 to 1. Su on CNBC: "Each of us could have 2 or 3 or even 5 or 10 agents doing work on our behalf. That means you need a lot more CPU compute."

WOLF

88,438 views • 2 months ago

The computer in Minecraft, got bigger! Ryan Boulds recreated real a CPU using redstone logic gates, adders, registers, memory. The build includes over a million blocks and can run arithmetic, comparisons, and even custom programs. He designed machine language to control it.

The computer in Minecraft, got bigger! Ryan Boulds recreated real a CPU using redstone logic gates, adders, registers, memory. The build includes over a million blocks and can run arithmetic, comparisons, and even custom programs. He designed machine language to control it.

Brian Roemmele

295,417 views • 8 months ago

When $NVDA talks about a $20B CPU opportunity, you should immediately think $ARM because Arm collects a royalty on every Vera CPU that ships. Its hyperscaler CPU share should keep climbing as the AI data center world gets more customized, more power-constrained and more workload-specific and that plays directly to what Arm is built for which is efficiency at low power and an ecosystem broad enough that everyone designs against it. That makes Arm a toll collector sitting underneath an enormous share of the world's computing.

When $NVDA talks about a $20B CPU opportunity, you should immediately think $ARM because Arm collects a royalty on every Vera CPU that ships. Its hyperscaler CPU share should keep climbing as the AI data center world gets more customized, more power-constrained and more workload-specific and that plays directly to what Arm is built for which is efficiency at low power and an ecosystem broad enough that everyone designs against it. That makes Arm a toll collector sitting underneath an enormous share of the world's computing.

Shay Boloor

87,755 views • 1 month ago

From our most popular CPU and GPU to the amount of countries we shipped to, this is our 2025 wrapped. (plus a hidden game as usual lol)

From our most popular CPU and GPU to the amount of countries we shipped to, this is our 2025 wrapped. (plus a hidden game as usual lol)

Ironside

13,821 views • 7 months ago

** Sega Genesis 3D engine update 4 ** Never can leave a good rabbit hole undug ! .. updates since last update : Changed frame buffer from a VDP tile friendly buffer to a linear buffer which needs CPU translation , which speedup drawing a LOT not having to worry about tile boundaries albiet slows buffer sending to VRAM. The interior filling of triangles now is running at 1.5c ( 68k cycles ) per pixel ! however sending the buffer is twice as slow per byte as we need the CPU to send the buffer to VRAM to write to the tile format the VDP needs, rather than DMA directly to VRAM . Overall speedup 25% + as the drawing speedup is much greater than the frame buffer slow down. Optimised Line drawing and Triangle filling -near optimal now for the linear frame buffer. Triangle drawing might get a little bit more yet. Quad drawing is next on the list as that will speedup drawing quads. Some gains will come from been smart about partial clearing of RAM buffers and partial sending to VRAM buffers, rather than send the whole buffer. Vertice rotation and projection needs a lot of optimising .. i expect good gains to come from this - this is all in C at present and all calced in real time. Line and Triangle drawing are in assembly but all vertex manipulation is in C. #SGDK #MegaDrive #SegaGenesis

Sega Genesis 3D engine update 4 Never can leave a good rabbit hole undug ! .. updates since last update : Changed frame buffer from a VDP tile friendly buffer to a linear buffer which needs CPU translation , which speedup drawing a LOT not having to worry about tile boundaries albiet slows buffer sending to VRAM. The interior filling of triangles now is running at 1.5c ( 68k cycles ) per pixel ! however sending the buffer is twice as slow per byte as we need the CPU to send the buffer to VRAM to write to the tile format the VDP needs, rather than DMA directly to VRAM . Overall speedup 25% + as the drawing speedup is much greater than the frame buffer slow down. Optimised Line drawing and Triangle filling -near optimal now for the linear frame buffer. Triangle drawing might get a little bit more yet. Quad drawing is next on the list as that will speedup drawing quads. Some gains will come from been smart about partial clearing of RAM buffers and partial sending to VRAM buffers, rather than send the whole buffer. Vertice rotation and projection needs a lot of optimising .. i expect good gains to come from this - this is all in C at present and all calced in real time. Line and Triangle drawing are in assembly but all vertex manipulation is in C. #SGDK #MegaDrive #SegaGenesis

Shannon Birt

15,280 views • 3 months ago

$AMD will become a multi-trillion dollar company. The AI boom is no longer just about GPUs. In early AI data centers, the CPU-to-GPU ratio was around 1:8. Now it’s moving closer to 1:1 because agentic AI requires dramatically more CPU compute. Lisa Su: “Based on the demand signals we are seeing today and the structural increase in CPU compute requirements driven by agentic AI, we now expect the server CPU TAM to grow at greater than 35% annually, reaching over $120 billion by 2030.” Add to that the 6GW AI infrastructure deals with $META and OpenAI, plus deep collaboration on multiple future chip generations, and it becomes clear why $AMD is positioned to compound for years. I’m not chasing $AMD here after a +110% move in just over a month. But the long-term story remains intact.

$AMD will become a multi-trillion dollar company. The AI boom is no longer just about GPUs. In early AI data centers, the CPU-to-GPU ratio was around 1:8. Now it’s moving closer to 1:1 because agentic AI requires dramatically more CPU compute. Lisa Su: “Based on the demand signals we are seeing today and the structural increase in CPU compute requirements driven by agentic AI, we now expect the server CPU TAM to grow at greater than 35% annually, reaching over $120 billion by 2030.” Add to that the 6GW AI infrastructure deals with $META and OpenAI, plus deep collaboration on multiple future chip generations, and it becomes clear why $AMD is positioned to compound for years. I’m not chasing $AMD here after a +110% move in just over a month. But the long-term story remains intact.

Daniel

39,585 views • 2 months ago

*** SEGA GENESIS/MEGADRIVE - SCALING PART 2 *** Whats better on a Friday than seeing some scaling effects on the Megadrive ? .. nothing, so read on ... In the previous part we were software scaling in either axis by a given factor, but I couldn't change the scale factor per scanline on the same frame, so I couldn't skew the base image for tilting into screen eg Mode 7 type effects. - One issue was it was scaling column by column which got wrecked for performance trying per scanline adjustments. So I converted to a row scaler rather than column, this allowed expansions and contractions on a per scanline basis. - Speed up the code significantly , now running a sprite load + music + scaling on cpu with ~50% cpu free. Relied heavily on Python scripts I wrote to generate the 68k assembly for this as it was mind numbing labourious. In doing so I got the scripts competing with each other to come up with the fastest method for each scale , I'm starting to like python ;-) - Tried all sorts to speed up the horizontal interupt - handles vertical scaling, exotic methods eg unsafe interupts / racing the beam & updating the vertical scroll every X cpu cycles, in the end the Z80 cpu (audio) stealing the 68k cpu bus intermittendly just killed these ideas as it would only be 95% stable, ended up just doing smarter interupts that saved a lot of cpu instead. - The good and the bad, spent too long on this is the bad, the good is we will need it in Lufthoheit in a few places to make up for that !! Carsten666 CYBERDEOUS - Crouzet Laurent #SGDK #SegaMegadrive #SegaGenesis

* SEGA GENESIS/MEGADRIVE - SCALING PART 2 * Whats better on a Friday than seeing some scaling effects on the Megadrive ? .. nothing, so read on ... In the previous part we were software scaling in either axis by a given factor, but I couldn't change the scale factor per scanline on the same frame, so I couldn't skew the base image for tilting into screen eg Mode 7 type effects. - One issue was it was scaling column by column which got wrecked for performance trying per scanline adjustments. So I converted to a row scaler rather than column, this allowed expansions and contractions on a per scanline basis. - Speed up the code significantly , now running a sprite load + music + scaling on cpu with ~50% cpu free. Relied heavily on Python scripts I wrote to generate the 68k assembly for this as it was mind numbing labourious. In doing so I got the scripts competing with each other to come up with the fastest method for each scale , I'm starting to like python ;-) - Tried all sorts to speed up the horizontal interupt - handles vertical scaling, exotic methods eg unsafe interupts / racing the beam & updating the vertical scroll every X cpu cycles, in the end the Z80 cpu (audio) stealing the 68k cpu bus intermittendly just killed these ideas as it would only be 95% stable, ended up just doing smarter interupts that saved a lot of cpu instead. - The good and the bad, spent too long on this is the bad, the good is we will need it in Lufthoheit in a few places to make up for that !! Carsten666 CYBERDEOUS - Crouzet Laurent #SGDK #SegaMegadrive #SegaGenesis

Shannon Birt

11,070 views • 1 year ago

Flying a simulated spacecraft controlled by a ZX Spectrum and Sinclair BASIC my first computer and programming language. Terribly inefficient right now because the serial port is so slow and the CPU spends lots of cycles bit banging to talk to it. There's a Python program in between which talks to KRPC and translates the important numbers to the serial port for the Spectrum to work from.

Flying a simulated spacecraft controlled by a ZX Spectrum and Sinclair BASIC my first computer and programming language. Terribly inefficient right now because the serial port is so slow and the CPU spends lots of cycles bit banging to talk to it. There's a Python program in between which talks to KRPC and translates the important numbers to the serial port for the Spectrum to work from.

Scott Manley

62,421 views • 6 months ago

How To Beat The CPU Every Time This Sunday we’re getting a Gauntlet-style CPU event where you have to go 10–0 to earn a 95 OVR BND Super Bowl player. You can beat the CPU consistently by calling this play. Formation: Nickel 3-3 Dbl Mug Play: Mid Blitz Setup 1.Pull The Safety Manned Up To The HB Over The Center 2.Tap UP on the D-Pad to open the Substitution Menu (this player-locks you). 3.Hold DOWN on the left stick. 4.Engage the center as the ball is snapped. Hopefully this was helpful! Feel free to Bookmark this for later, and Follow Me, Hexied, for more Madden content like this!

How To Beat The CPU Every Time This Sunday we’re getting a Gauntlet-style CPU event where you have to go 10–0 to earn a 95 OVR BND Super Bowl player. You can beat the CPU consistently by calling this play. Formation: Nickel 3-3 Dbl Mug Play: Mid Blitz Setup 1.Pull The Safety Manned Up To The HB Over The Center 2.Tap UP on the D-Pad to open the Substitution Menu (this player-locks you). 3.Hold DOWN on the left stick. 4.Engage the center as the ball is snapped. Hopefully this was helpful! Feel free to Bookmark this for later, and Follow Me, Hexied, for more Madden content like this!

Hexied

89,118 views • 5 months ago