You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
How long should it take to reboot the MCU? I tried the scrollwheels reboot and 10 minutes later it's still not back on. I'm wondering if this is an indication of eMMC starting to fail.
Interestingly enough, you can hear the system trying again and again as the HVAC system turns on for a bit for each cycle. I can also see the notification "Autopilot features unavailable" appearing, then it'd go away and autopilot works, repeat.
I ended up parking the car and now I've come back to it several hours later and it's turning on finally.
It should only take about a minute or so... Seems like your emmc is failing.How long should it take to reboot the MCU? I tried the scrollwheels reboot and 10 minutes later it's still not back on. I'm wondering if this is an indication of eMMC starting to fail.
Interestingly enough, you can hear the system trying again and again as the HVAC system turns on for a bit for each cycle. I can also see the notification "Autopilot features unavailable" appearing, then it'd go away and autopilot works, repeat.
I ended up parking the car and now I've come back to it several hours later and it's turning on finally.
When the EMMC chip is healthy: about 90 seconds before you see the T logo. And another 90 seconds before the UI is loaded. And then another few minutes to load the 3G/LTE connectivity.How long should it take to reboot the MCU? I tried the scrollwheels reboot and 10 minutes later it's still not back on. I'm wondering if this is an indication of eMMC starting to fail.
If you are up for some serious reading check out this site. The author is on here frequently. I am not going to post his TMC name. He can reveal himself when he wishes too. This is a read way over my head. But I learned a lot reading his content. And he answered many questions that I posed to him.How long should it take to reboot the MCU? I tried the scrollwheels reboot and 10 minutes later it's still not back on. I'm wondering if this is an indication of eMMC starting to fail.
Interestingly enough, you can hear the system trying again and again as the HVAC system turns on for a bit for each cycle. I can also see the notification "Autopilot features unavailable" appearing, then it'd go away and autopilot works, repeat.
I ended up parking the car and now I've come back to it several hours later and it's turning on finally.
I guess this happens because the IC doesn't know your brightness setting until it reads it from the CID. So it will flicker (and if you try to change brightness, it might tell you it's at -5%) until the CID awakes. At least, this is what happens in my car.Interesting that the IC after the reboot flickers quite a bit while the MCU is trying to reboot.
I guess this happens because the IC doesn't know your brightness setting until it reads it from the CID. So it will flicker (and if you try to change brightness, it might tell you it's at -5%) until the CID awakes. At least, this is what happens in my car.
When the EMMC chip is healthy: about 90 seconds before you see the T logo. And another 90 seconds before the UI is loaded. And then another few minutes to load the 3G/LTE connectivity.
10 minutes is definately not a good sign.
4 to 5 minutes before the T shows or before the UI shows? Either way it is not normal, with a normal/healthy emmc they always boot like clockwork: 90 seconds till T logo, then another 90 seconds till UI shows. 3 Minutes total (besides the activating of 3G/LTE which can take some longer depending on coverage etc). Everything slower could be a sign something is wrong.So when mine takes between 4 to 5 minutes that should be normal? It definitely used to be much faster than that.
4 to 5 minutes before the T shows or before the UI shows? Either way it is not normal, with a normal/healthy emmc they always boot like clockwork: 90 seconds till T logo, then another 90 seconds till UI shows. 3 Minutes total (besides the activating of 3G/LTE which can take some longer depending on coverage etc). Everything slower could be a sign something is wrong.
Was curious, so while supercharging this morning thought I would supply another sample. I have a 64GB Swissbit eMMC; was upgraded over a year ago, and have not had any other issues or repairs on this mcu1.
94 seconds to see T
2 min 47 s to get UI, and wifi was already connected when UI was visible
Looks like Luckylukes info is bang on.
Yeah. The new software reports when the eMMC is failing for at least some of the chips Tesla used. I heard there were three chip types. The message appears on your display if you have the lucky version. For the rest though, you never get the message and just have to wait for MCU1 to die. I have had dozens of crashes (and did an FPGA reflash that I would not recommend) and now have removed my USB drive at their their request which stopped the crashes, but of course now I have no no USB music or sentry/dashcam recording....Has anyone else heard this?
Never had any warnings in the car.
Performed autodiag on MCU. Daughterboard should be replaced proactively.
Aren't the numbers worse if the car is rebooted right after a long rest, for example the overnight sleep?
10 minutes normal...that sounds ridiculous. I'm throwing the BS flag on them. Maybe common but not normal. My MCU1 was taking over 3 1/2 minutes to boot to the Tesla T before I upgraded to MCU2.So I asked for service from Tesla and they told me it's normal for reboots to take 10 minutes. I don't even know how to respond. It often takes even longer so I'm going to time it.
[edit]This time it took 21 minutes for the T to even display on the screen.