Please report final results, sorry the original post has gotten really long, I think I did specify doing multiple at some point. And I was hinting when I mentioned #1396 when I mentioned factory resets. It is really weird and I'm not sure if its is combo of reboot and factory resetting, and sometimes update. We do find that eventually it resolves the issues after much pain and suffering.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Please report final results, sorry the original post has gotten really long, I think I did specify doing multiple at some point. And I was hinting when I mentioned #1396 when I mentioned factory resets. It is really weird and I'm not sure if its is combo of reboot and factory resetting, and sometimes update. We do find that eventually it resolves the issues after much pain and suffering.
X Fan
Active Member
I finally convinced the Service center to replace the daughterboard. X no longer has blank screen issue but now phone app is not able to open the vehicle. SW updated last night to 48.12.1
Q: could that be something Tesla needed to do programming wise to the daughterboard or SW issue or...not relevant to either issue.
Thanks
Q: could that be something Tesla needed to do programming wise to the daughterboard or SW issue or...not relevant to either issue.
Thanks
Yes, that is most likely that they forgot to program the "car keys" on the new daughterboard. They should be able to fix that remotely.
X Fan
Active Member
Did a longer drive today and still had issues. After a little over an hour of driving, LTE started resetting, temp on IC started resetting, MCU responsiveness was terrible, audio went wonky, ugh...
This happened to me too. I think it might be some bug / memory leak with the new software, maybe not the eMMC itself?
My situation- new eMMC replaced with a better one many months ago and many software updates and reboots ago. Happened 3 times in my long drive (CLT to Boston and back), 2 times while supercharging.
1st time - I tried changing the route while charging in VA Supercharger to avoid traffic. The MCU got stuck in "calculating" state - became super laggy, with music stuttering etc, and eventually hung. tried rebooting but nothing I did worked. Eventually pulled the MCU fuse from the frunk and put it back. It rebooted and worked just fine after that.
2nd time - while driving, I lost LTE a couple of times in the mountains. I tried changing music streams and the screen became super laggy. Just waited it out without doing anything and it fixed itself.
3rd time - Again while supercharging, it was past midnight and I think the car went into sleep / reboot mode. I believe the car does this low power / reboot cycle after midnight where it takes the center screen some time to boot up, but this was both screens (including IC) and it took way longer. Eventually the 2 button reboot got the car started. Once started, all good again.
@appleguru any insights?
No specific insights other than to say that I have been experiencing the exact same symptoms on my car (with a factory emmc). It has been into service about half a dozen times for this issue (car is still under warranty), and Tesla tells me every time that "everything is fine" and meets their spec and refuses to replace any hardware. They "suggest upgrading to MCU2" (at my expense). They usually perform a factory reset, or an FPGA reflash and/or software redeploy, which sometimes helps for a few hours, but inevitably the issues return.
I agree that the current MCU issues seem to largely be firmware based, and honestly started around the v9 ("full screen map") release. Not sure they care enough to actually fix these issues though at this point, but we know the Tegra can perform well with properly written software that's optimized for it.
LuckyLuke
Model S P90DL
Whenever you notice some laggyness try switching to radio (like AM/FM) instead of streaming music. The spotify and tunein can sometimes hog the cpu especially when cell reception is bad.
Thanks I'll try that next time. Definitely would have helped with the 2nd time it lagged. Not sure what else I could have done other than pulling the fuse the other times though. Tesla really needs to fix their software. I don't need any more games if I can just get some good bug fixes.
So things have moved faster than I expected. NHTSA has asked Tesla to perform a recall on the eMMC issue.
MCU Recall Request INRM-EA20003-11321.pdf
It appears that Tesla has the choice if they just want to do the recall as requested, or they have until January 27th to respond and explain why they think they don't need to perform a recall.
MCU Recall Request INRM-EA20003-11321.pdf
It appears that Tesla has the choice if they just want to do the recall as requested, or they have until January 27th to respond and explain why they think they don't need to perform a recall.
X Fan
Active Member
Had my daughterboard replaced last month after much persistence to the service center (got the usual blah blah RE: new set would fix it, pay $2500, etc)
My vehicle back is to normal. Hopefully,Tesla reacts favorably to the pressure.
My vehicle back is to normal. Hopefully,Tesla reacts favorably to the pressure.
FlatSix911
Porsche 918 Hybrid
Tesla
More information here... NHTSA asks Tesla to recall Model S and Model X over MCU fiasco - Electrek
More information here... NHTSA asks Tesla to recall Model S and Model X over MCU fiasco - Electrek
mspohr
Well-Known Member
That doesn't look like an eMMC memory problem. Missing scan lines is something with the screen driver or screen connection.
You might want to consider getting the MCU2 upgrade. Everyone seems to be very happy with it. Probably not much more expensive than repair of MCU1.
This is typically the result of an FPGA failure, which is on the main MCU board and not the tegra.
With that said, my MCU (under warranty) has exhibited the same symptoms several times (spewing FPGA errors in the logs), and to date, tesla has refused to replace any hardware and has only done "software" fixes (including manually re-flashing the FPGA firmware, which usually happens every time an MCU FW update happens anyways).
Similar threads
