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

Preventive eMMC replacement on MCU1

This site may earn commission on affiliate links.
I read somewhere thare there is a removal card on the MCU : maybe we only have to switch this card : take the one with the car on the old MCU and replace it on the donor MCU ?

Someone here can confirm/invalidate this ?

I think that is only for the very early Model Ss. They went to soldered on eMMC in 2013. But the whole point is that whatever the memory is it has failed, so you can't just move it to the new MCU as that would move the broken part.
 
Hmmm. I had a completely dead MCU. I drove the car for a few weeks. What lights are you trying to turn off? I never turn mine off manually.

My MCU screen was totally blank, some lights inside. Could drive it. Then I had the car on when I unplugged the thing and it won't move anymore. Also driving lights got stuck on automatic.

On other note, tried to read out the emmc without desoldering today. Not much success. The board draws 1,5A on three volts, and that seems to be burned on the tegra processor, as that gets hot after a while.

Tried to force that and the power management chip off/reset state, but couldn't. I suppose no one has schematics for this board on hand?
 
  • Informative
Reactions: rooter
A month later: eMMC still not swapped. However, it is possible to drive without the processor card.

Even a data recovery specialist couldn't get any data out from the desoldered chip. No way to know if it was totally wasted when I got it or destroyed while desoldering.
 

Attachments

  • look_ma_no_cpu.jpg
    look_ma_no_cpu.jpg
    180.5 KB · Views: 496
I think that is only for the very early Model Ss. They went to soldered on eMMC in 2013. But the whole point is that whatever the memory is it has failed, so you can't just move it to the new MCU as that would move the broken part.

They still have the removable SD-card, but from what I've heard that is only used for debugging purposes. eg. it can write specific debugging data on request (eg. reportbug feature, but also from Tesla headquarters).

Best solution would be to have a removable device as main storage drive. eg a removal SSD or removable SD card. Tesla will probably not do this, since that makes rooting the MCU childsplay.
 
They still have the removable SD-card, but from what I've heard that is only used for debugging purposes. eg. it can write specific debugging data on request (eg. reportbug feature, but also from Tesla headquarters).

Best solution would be to have a removable device as main storage drive. eg a removal SSD or removable SD card. Tesla will probably not do this, since that makes rooting the MCU childsplay.
A proper SSD is way more expensive then this eMMC solution. Still, eMMC isn't a bad thing, but what they use now:

- Is too small
- They write too much
- It wears out
 
A proper SSD is way more expensive then this eMMC solution. Still, eMMC isn't a bad thing, but what they use now:

- Is too small
- They write too much
- It wears out

Yes its expensive, but doesn't fail as easily either. Not much use in having drivetrains that last 1.000.000 kms if the rest of the car doesn't.
Even a bigger eMMC (as used in MCU2) will eventually fail. Tesla still writes _a lot_ to syslog on the eMMC.

It's a device that will require replacement sooner or later. IMHO a device that needs replacement has to be replaceable. They could use an hardware encrypted drive for all I care. But having to replace the entire MCU just because of a bad memory chip is a design flaw IMHO.
 
Any progress here?
So @Lucky Luke has replaced his eMMC and ran into some software problems as he could’t read the data properly from his old eMMC.

I just got back from holiday and starting to pick things up again. Need to puzzle it all together and how to do what and when.

I am currently going through the firmware of the car (have the binaries) and just trying to see how it’s all tied together. Seems like a lot of Bash scripts doing stuff :)
 
So @Lucky Luke has replaced his eMMC and ran into some software problems as he could’t read the data properly from his old eMMC.

I just got back from holiday and starting to pick things up again. Need to puzzle it all together and how to do what and when.

I am currently going through the firmware of the car (have the binaries) and just trying to see how it’s all tied together. Seems like a lot of Bash scripts doing stuff :)

It's probably been mentioned, but could the format from an older removable eMMC work as a base image?

When you say you bought a "socket" do you mean a removable card socket or a socketed chip socket?
 
It's probably been mentioned, but could the format from an older removable eMMC work as a base image?

When you say you bought a "socket" do you mean a removable card socket or a socketed chip socket?
It probably could. The MCU boots from a read-only squashfs partition. This is signed by Tesla, you can’t change this.

There is another partition which contains the car specifics like the VIN and such, you would need to modify that for your car.

I have a AllSocket eMMC adapter which I can use to read and write eMMCs. You need to de-solder the chip from the MCU to do this.