Just uploaded a fixed version of the MCU removal tutorial.
Mods: please remove my previous post with the old link
Mods: please remove my previous post with the old link
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.
I'm tellin' you. Better not. You'll get shut out by those who matter. Notice that Luke isn't sharing any details?
I'm the author and I'm still down. Got some help from an old friend for a bit, but not lately.
My articles are 'down for some reason'? Read my note more carefully. Somebody saved my article in case -I- took it down? Be honest; you saved it case it got taken down by outside forces. Don't bite the hand that fed you.
There's an easy way to recover hard-to-read chips which was in one of my posts over there. Research recovering flash data.
@rooter has done a great job providing lots of information and expertise on this issue. I have started to think similar if a separate component of the chip is going bad. We refer to this as a single chip, but there is really much more inside. We have seen reports of the chip being disassembled and new controller put in to read the content with @widodh recovery. as @whitex has mentioned the failure rate of eMMC chips is on a bell curve. We have seen chips that went well beyond the 3000 writes. We have seen chips with heavy corruption on chips much less that 3000 writes, sometimes around 1000-2000. Only time will tell how much better this upgrade is than the original. But we do know that in several years 3000 writes can happen so having a chip that has much more writes is expected to last longer. The pSLC mode we use gives it 20k write which we like a lot more than 3000, plus have double the space so there is many more write cycles due to the chip's wear leveling. We will be continuing to use the Swissbit until we or someone finds a even better chip. And we expect the current chip to outlast the car, however we would not hesitate to spend a few more dollars to offer a even better upgrade.
Unfortunately at this time we don't have to expertise to identify the exact failure and simply identify the chip as less then reliable enough to use and need a replacement.
Anytime we discover improvements we incorporate into the fix.
While an interesting theory, the performance data does not support it, at least not for the Swissbit pSLC case. RAID1 configuration would mean you get twice the sustained read performance and the same (or slightly slower) write performance, but when you compare the specs for pSLC vs. MLC modes of Swissbit, that is not he case - write speeds get most of the performance boost, while read is faster but not as dramatically as writes.I am beginning to suspicion that this 'endurance-grade' that we see on SD cards simply means they are using the dual channels of the chip controller, and dividing the chip into two halves like RAID1. (mirroring) This means that your chances of recovering the data are doubled, the chip capacity is halved, and coincidentally the speed is increased as the non-busy channel is chosen next.
The Swissbit chip as-is is likely to outlast other electronics in the car, but you can buy it also set to dual-channel mode. I don't remember what the secret code word is for this mode, but it's just a bit set.
If you shut off the car (via the big MCU screen) before pulling MCU fuse, the IC should stay off. Not sure which fuse is for the IC, but that would be your next step.I just pulled my MCU for eMMC replacement. I was planning on not replacing the MCU till I got the chip replacement back as I won't be driving the car. Have car on a charger but the dash screen is constantly on. Is there a way to turn off power to this? (Pull another fuse, disconnect 12V?) Would rather avoid dealing with the MCU connectors till I get the chip back. Thanks.
For those that have had MCU failures, this may be of interest. There's at least *some* possibility that the cars could be recalled for free (or reimbursed) replacements of the original eMMC chips. If you've replaced an MCU, you might be well-advised to add your complaints to the NHTSA database as they're only reporting 11 (!) complaints.
https://www.cnbc.com/2020/06/24/us-opens-probe-into-tesla-model-s-after-touchscreen-failure-reports.html
For those that have had MCU failures, this may be of interest. There's at least *some* possibility that the cars could be recalled for free (or reimbursed) replacements of the original eMMC chips. If you've replaced an MCU, you might be well-advised to add your complaints to the NHTSA database as they're only reporting 11 (!) complaints.
https://www.cnbc.com/2020/06/24/us-opens-probe-into-tesla-model-s-after-touchscreen-failure-reports.html
I don't see a lot of risk in attempting to fix a failed ECU. Soldering the eMMC would be about it. Copying the data off the old eMMC to the new one shouldn't be a big issue. Caveat: I've been a Linux tech since 2002.