3 ms·
> The Tesla firmware wasn't very big at the beginning, [...] the firmware has grown, leaving very little room for the logging to take place. That means individu
by michaelt 7y ago
> The Tesla firmware wasn't very big at the beginning, [...] the firmware has grown, leaving very little room for the logging to take place. That means individual sectors suffer from lots of data being written in a short amount of time, further accelerating the wear.
My understanding was modern flash memory wear levelling would swap regularly-written and seldom-written sectors around, allowing for even wear across the disk even if it was 95% full all the time. Is it established that Tesla doesn't have this feature?
- planteen 7y agoI'm not sure exactly what eMMC part they are using, but the SDHC spec doesn't explicitly require wear leveling. A part could implement it, but it's not a given.
- codeulike 7y agoIt does, but the article says that the car logs a lot of data and so consequently all sectors get wear. See here: https://insideevs.com/news/376037/tesla-mcu-emmc-memory-issue/ https://insideevs.com/news/376037/tesla-mcu-emmc-memory-issu...
- oarsinsync 7y agoIt's also possible that older Tesla vehicles do not have modern flash memory.
- benj111 7y agoThat would be bad for this use case? I want the firmware working, I don't much care if data logging stops working.
- rcxdude 7y agoWhile I might expect an SSD to use such a strategy, an embedded flash chip doing so is just as likely to be a misfeature, because when the flash does fail you may lose data other than that already being written, which makes it impossible to keep the system even limping along without any logging.