Kiveszed az alaplapot, kiforrasztod a csippet, beforrasztasz egy másik csippet, aztán a kernelben lekapcsolod a loggolást.
Szerintem egy ügyes műszerész pár perc alatt megcsinálni, miközben a fél kezét a seggébe dugja...
According to Phil Sadow who is in the Rich Rebuilds video, the problem is the MCU is doing Linux kernel logging continuously. Logging video too probably makes it worse.
I was just starting out as an Electronic Engineer when flash memory was first introduced and I did a design with the first generation flash memory. All flash memory has a max write limit per cell. It's always been there. The limit has improved, but it is still there. Constantly write to flash memory and it will eventually fail, no matter the quality.
There was someone who did a stress test of SSD drives writing massive loads to a number of different SSDs until they failed. All lasted past their design limits, but all failed eventually.
The problem that Tesla did was they left the Linux logging turned on, which provides no useful information for service. (The logs service check are written to a removable CD card on the MCU which can be replaced very easily.) This is written to a soldered in flash memory part that eventually fails when the write limit of the chip is reached and then the MCU quits working. Phil Sadow repairs these failures by replacing the chip and turning off the logging.
He said in the Rich Rebuilds video that Tesla has not changed this with new MCUs, it's just they are young enough they haven't failed yet.
