You need a Linux OS.Does my Facelift Model S from 06/2016 with original MCU (MCU1) also have the MicroSD card with navigation data?
Because I also had some issues regarding navigation system in the past few days/weeks. It often doesn't load and only shows the message that the navigation system is initializing.
So can I take the original MicroSD out of my MCU, copy the data onto a new 32GB MicroSD, stick it in my MCU and the problems should be solved?
I don't think you need Linux to make a 1:1 bitcopy image from a sd card. I assume there are Windows tools available that can do this just fine.
Still keeping the old card!
Hi all. Just a informative / warning message from me
There is now a new, until now largely unknown, reason for getting a full black center screen on a first generation MCU1.0 found on cars up to and including 2015. This report does not cover the newer 1.5 MCU found in 2016 and newer cars, however a similar problem could occur in that system as well.
In the past weeks I have seen some cars where the EMMC was already replaced before (most by 3rd party, but also one that was replaced by Tesla).
The problem: the main screen went black again, and a error message pops up in the Instrument Cluster "center screen not functional". Exactly like you would see when the EMMC chip fails.
Some cars had been to Tesla Service Center already for this problem. At the Tesla Service Center they usually diagnosed it as "MCU needs to be completely replaced" and one customer was even told the problem was caused by "third party EMMC repair". Lucky for these customers they contacted me to find out what the problem was exactly.
The car owners all reported that the problems started with navigation issues, slow calculating routes, nav icon keeps spinning, new maps trying to download over wifi, etc. After scroll-wheel rebooting the MCU it stays black. Appearing almost exactly when EMMC chip is failing.
I have investigated these cases and they are all related to a failing navigation maps MicroSD card (this 16GB MicroSD card is located on the MCU1.0 mainboard). Apparently when the navigation card dies this can cause the entire system to crash and not even start anymore (not even when power cycling the mcu).
Even when the MicroSD card was completely removed or replaced the system would still not start and will still give a black screen. Huh!?
This was all on 2013-2015 MCU1.0 cars, newer MCU1.5 cars from 2016 and up have replaced the MicroSD card with a internal/soldered EMMC chip for the maps.
Anyway: a dead/corrupt MicroSD card can prevent the system from starting up completely. The Tegra computer will boot in what that is called "Recovery" mode and it will also write some changes to the boot environment stored on the NOR chip which is located on the Tegra module (this Spansion NOR chip contains the bootloader, environment and kernel images). This change prevents the Tegra from booting to normal mode. Wut?!
To fix this problem you will need to do several things:
1) Replace the MicroSD card with a new one (16GB recommended, but can be larger as well)
2) Fix the environment on the NOR chip on the Tegra module (mtd7 partition, swap boot bank, fix fail count)
3) Partition the new MicroSD card with the correct partitions (can use nav-sdcard-format.sh for that)
4) Install the correct navigation maps on the MicroSD card (EU maps are about 8GB in size)
Step 1 can be done easy by swapping the card in the MCU (accessible from the side of the MCU housing)
Step 2 is way more complex and only possible when you have full read/write access to the NOR chip. Most repair shops that deal with EMMC repairs will be able to do this.
Steps 3&4 can be done on a (Linux) pc if needed, but can also be done on the MCU itself (need root access for that).
If you go to Tesla with this problem they will most certainly tell you that "The entire MCU needs to be replaced", or even throw in a "Problem caused by 3rd party repair" excuse. All that for a cheap MicroSD card...
Considering these cars are getting older, the chances are increasing that more owners with MCU1.0 cars will eventually face a failing navigation MicroSD card.
Conclusion: If you see reports on black screens then it could be a navigation MicroSD issue. Even on cars that already had the EMMC chip replaced (by Tesla or by third party).
If you face any MCU1 related issues and don't want to go to Tesla feel free to PM me for help.
My sound issue was solved by reconnecting the black MCU plug on the bottom right that somehow got disconnected during removal of the SD card. I literally checked all fuses from boxes 1-3 then realized it’s gotta be a loose connector. I didn’t see it at first since there are like 10 connectors and it was covered by all the other wires when accessing it from the passenger seat.
Holy crap those are expensive. I assume their longevity and durability match the price? Might be overkill; I’ll let some computer experts chime in, but here is an article to browse: My Kingston datatraveler 64gb has been flawless for over a year.
1. Got itNow I'm in doubt about my prior statement on the MCU1.5 units. If your MCU1.5 still uses the external MicroSD card for maps instead of the internal secondary emmc then yes you can replace the current/old with a new card ofcourse.
1. I have not tested this but since there is quite some reading done while calculating a route then the answer is yes: replacing the card with a better/recent one will improve the performance a little bit. I would not expect a miracle though
Don't forget the Google map tiles that are displayed on the main screen are real-time downloaded over the air (and cached on the primary emmc). Only the route calculation itself is done from the microsd (or secondary emmc) maps data.
2. There is a file on partition 3 of the primary emmc (this partition is mounted as /var) at (/var)/etc/maps-device , this file content is either "/dev/mapsSD" or "/dev/mapsMMC". The former tells the system to read the nav data from SD, the latter from the secondary EMMC.
In your case I expect it to say SD since you tested this by taking the card out.
There is another file on the primary emmc called (/var)/etc/map-updater/BANK_(A or B).size , this file tells the system the size (in bytes) of the sqfs image and wether it is located on partition 1 (bank A) or partition 2 (bank B).
3. Yes. There are always 2 partitions. Since version 2019 the maps are in squashfs format. So I assume your partition 1 is either the EU-2019.20-10482 or the EU-2019.21-12489 sqfs image. Your partition 2 is either empty or it contains some older maps (which used to be stored in ext3 fs).
I can send you a 16GB image to write to the new card but I need to know first which map version you have is it 2019.20 or 2019.21 ?
(I put the same version map sqfs on both p1 and p2 so it does not matter if your .size file says the maps are located on bank A or B)
However, if your current microsd card is still readable you don't need my image at all, you can just make a 1:1 bitcopy from the current card.
Can you send me your 16GB image file?Now I'm in doubt about my prior statement on the MCU1.5 units. If your MCU1.5 still uses the external MicroSD card for maps instead of the internal secondary emmc then yes you can replace the current/old with a new card ofcourse.
1. I have not tested this but since there is quite some reading done while calculating a route then the answer is yes: replacing the card with a better/recent one will improve the performance a little bit. I would not expect a miracle though
Don't forget the Google map tiles that are displayed on the main screen are real-time downloaded over the air (and cached on the primary emmc). Only the route calculation itself is done from the microsd (or secondary emmc) maps data.
2. There is a file on partition 3 of the primary emmc (this partition is mounted as /var) at (/var)/etc/maps-device , this file content is either "/dev/mapsSD" or "/dev/mapsMMC". The former tells the system to read the nav data from SD, the latter from the secondary EMMC.
In your case I expect it to say SD since you tested this by taking the card out.
There is another file on the primary emmc called (/var)/etc/map-updater/BANK_(A or B).size , this file tells the system the size (in bytes) of the sqfs image and wether it is located on partition 1 (bank A) or partition 2 (bank B).
3. Yes. There are always 2 partitions. Since version 2019 the maps are in squashfs format. So I assume your partition 1 is either the EU-2019.20-10482 or the EU-2019.21-12489 sqfs image. Your partition 2 is either empty or it contains some older maps (which used to be stored in ext3 fs).
I can send you a 16GB image to write to the new card but I need to know first which map version you have is it 2019.20 or 2019.21 ?
(I put the same version map sqfs on both p1 and p2 so it does not matter if your .size file says the maps are located on bank A or B)
However, if your current microsd card is still readable you don't need my image at all, you can just make a 1:1 bitcopy from the current card.
I would submit a service request and state your maps no longer work after daughterboare replacement and then ask for your SD card to be reformatted.
Welcome to Tesla Service Center. They even don't care to replace a simple outdated microSD card to to replace it to a more contemporary card. according to my knowledge there is even not a significant price difference (price might vary according to your country). Some links bellow.
