Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

I retrofit MCU2, IC2, Tuner2, and FSD Computer into my HW2.0 Car

This site may earn commission on affiliate links.
Here's my story of my DIY HW2.0 retrofit for MCU2, IC2, TUNER2, and FSD Computer:

I want to begin this post by offering the most honest caveat I can: I do not encourage you to repeat anything I have done. In fact, now that Tesla is offering the MCU2 and FSD Computer retrofits officially, I highly recommend you go do that. MCU2 + FSD is wonderful. I am presenting this post to hopefully provide some guidance and entertainment to members of this great community – a place that I’ve found endlessly fun for the past several years during my Tesla ownership. I make no claims that the guidance offered below is correct or suited to your circumstances.

Towards the end of January, late one night while tinkering with my Tesla, I had a realization – I finally knew enough about the Model S/X hardware & software architecture to attempt one of the most involved retrofits I’ve ever done on a vehicle – an MCU2/IC2/Tuner2/APE3 retrofit into my HW2.0 MCU1 Model S. After a LOT of research, and with tons of help from others in this community (thank you to those that helped; you know who you are), I wanted to share my success story of retrofitting MCU2/IC2/Tuner2/APE3 to work in my car. All told – I have a fully working MCU2/IC2/Tuner2/APE3 with all the Theater, Arcade, Caraoke, FM Radio, Web Browser, Dashcam, Sentry, FSD visualizations and other goodies you would expect.

“But Tesla now offers an official MCU2/APE3 retrofit!” you say…” Why would you want to do a retrofit yourself?” Good question…there’s a couple reasons I chose to do this myself:

  • I completed the retrofit a couple months before Tesla finally came out with a public announcement that MCU2 retrofits were officially official. I’d been waiting for Tesla to follow-through on Elon’s never-ending tweets promising a retrofit was coming and finally just decided I’d do it myself.
  • Tesla charges $2,500 for the MCU2/IC2 retrofit and does not include the XM/FM Tuner2. I thought I’d try getting Tuner2 to work – which I did.
  • I found a person with a wrecked 2018 Model S who was willing to sell me the MCU2, IC2, Tuner2, and wiring harness out of the car – everything I needed from a hardware perspective for a reasonable price. All in, I saved roughly $1,000 doing this myself compared to asking Tesla to do it. Honestly though, I probably put 100+ hours into this project and went from knowing nothing to knowing a lot. I didn’t really save time/money; quite the contrary. I did this because it was a ton of fun.
  • I got the APE3 (FSD Computer) unit on loan from a friend. I did purchase FSD from Tesla and will have Tesla install my forthcoming APE3 unit whenever they actually do it.

Come along as I take you through my journey of retrofitting the MCU2/IC2/Tuner2/APE3 hardware into my HW2.0 car.

mcu2-png.531258
 
I don’t know that to be the case. I believe there may be other hardware requirements like SCCM which is different between hw1 and hw2 cars. I simply do not know because I never had an AP1 car. The ap1 car also has completely different front camera and lacks the repeater and pillar cameras. It won’t work with ap3 without serious modifications and wiring changes. I know someone that has done it - it was a Frankenstein project
 
I don’t know that to be the case. I believe there may be other hardware requirements like SCCM which is different between hw1 and hw2 cars. I simply do not know because I never had an AP1 car. The ap1 car also has completely different front camera and lacks the repeater and pillar cameras. It won’t work with ap3 without serious modifications and wiring changes. I know someone that has done it - it was a Frankenstein project
Have been carrying out assessment. Should be possible without any Frankensteinment.
The idea is to simplify the process:
1. Upgrade to AP2.0
2. Get approval from Tesla
3. Upgrade to AP3.0
 

Attachments

  • TMX 2015-2022 AP1 to AP2.0.pdf
    975.2 KB · Views: 137
Last edited:
  • Like
Reactions: Smalltom
Have been carrying out assessment. Should be possible without any Frankensteinment.
The idea is to simplify the process:
1. Upgrade to AP2.0
2. Get approval from Tesla
3. Upgrade to AP3.0
upgrade to ap2.0 is not all that easy.

you need to put in all the surround cameras, you need to put in the autopilot behind the glove box (there is no bracket so you need to make up something to hold it in place. It believe it needs different ultrasonics that were announced at the time of hw2.0 introduction. The rear camera reportedly also was changed to one that has heating element.
All of that needs harness changes throughout the car.

Chances of Tesla pproval for such changes are.... slim.
 
Someone is a glutton for punishment. Now that its been done by someone that knows what they are doing. And is explaining its not that easy. That should be sufficient warning. I believe it would be much easier, simpler, and less a risk regarding Tesla approval to simple sell the current one and find a used one with AP2.5/3.0 and drive it.
 
If anyone is in the market for doing this, I've been cleaning out my basement and came upon my EasyJtag, a stand, and probes that I used to do my own DIY MCU2 upgrade. You just need to place the probes and get writing! DM if you're in the market and we'll work something out.
 
  • Like
Reactions: Krash
If anyone is in the market for doing this, I've been cleaning out my basement and came upon my EasyJtag, a stand, and probes that I used to do my own DIY MCU2 upgrade. You just need to place the probes and get writing! DM if you're in the market and we'll work something out.
I am interested in DIY upgrade of Model 3 HW2.5 to FSD and seems like direct access to eMMC is the way to go if it is not encrypted. Any reasons why it would not work?
 
I know someone with an FSD computer (HW3) available for sale if you are interested.

 
I was able to get my MCU2 provisioned for my car by completely disassembling it and writing some key files using a BDM Table/Probes and a (slow) easyJtag box to read and write data to the MCU2’s emmc flash chip. MCU2 has a 64GB emmc chip (much bigger than MCU1’s), and only 32GB is provisioned, so there is lots of headroom for wear-leveling – it should last considerably longer than MCU1’s emmc chips that constantly fail.
View attachment 531267
Would you by any chance remember/share the pin assignments used to perform this dump?