Yes, it's still here: freerobby/tesla-service-manual
Watch out with the 'dd' command! If you by accident revert 'if' and 'of' you'll overwrite your eMMC!
And for this reason "dd" is humorously known as Disk Destroyer.
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.
Yes, it's still here: freerobby/tesla-service-manual
Watch out with the 'dd' command! If you by accident revert 'if' and 'of' you'll overwrite your eMMC!
Had one emmc unsoldered from a spare MCU. Reads fine, all 4 partitions. No fsck errors. Wrote it on 64gig new Swissbit. Expanded fs. All looks good.
I could have the new chip soldered back on that spare board, but I cannot test if it works. Cant power up an MCU just by 12V with no ext. cables and hardware. This whole center units comes from a salvage car, just for spares.
But until here everything works.
So I now consider going directly to my working MCU from my car. Lets see if a new chip will work. Will take over a week (shipping to the solder ship 2 times)
True. But as he said in the first sentence he did expand the filesystem on the chip.Sounds interesting. Remember, that it you just bitcopy / klone a 8 gig onto a 64 gig, you still only have a 8 gigi space availeble... As I remember due to the partisions
What kind of emmc reader are you using? Does Linux still see the partitions on the emmc?I got the actual chip of my MCU today back from desoldering. This time it is recognized by computer, but ddrescue fails to get anything out of it. Is there any other way to get the image? The IC computer card has a similar chip and IIRC someone had extracted an image from that and got the MCU to run with it.
Seems that the service center is a bit nearer again.
What kind of emmc reader are you using? Does Linux still see the partitions on the emmc?
Fair enough. But you do extend the lifetime of the MCU with another ~5 years.My 2 cents...
There's no point in premptively replacing the eMMC before it fails. Any replacement will fail eventually as well.
This might become a slowchat, but the disk size is recognized by your computer, but it doesn't show any partitions on it? That's not good news.I tried with allsocket usb 3.0 reader and with moorc emate socket-adapter stack inserted to a transcend usb sd reader.
I'm afraid only the disk is recognized, and not the partitions.
I got the actual chip of my MCU today back from desoldering. This time it is recognized by computer, but ddrescue fails to get anything out of it. Is there any other way to get the image? The IC computer card has a similar chip and IIRC someone had extracted an image from that and got the MCU to run with it.
Seems that the service center is a bit nearer again.
[98655.396676] sd 6:0:0:0: Attached scsi generic sg1 type 0
[98656.437560] sd 6:0:0:0: [sdb] 15155200 512-byte logical blocks: (7.76 GB/7.23 GiB)
[98656.439075] sd 6:0:0:0: [sdb] Write Protect is off
[98656.439078] sd 6:0:0:0: [sdb] Mode Sense: 21 00 00 00
[98656.440572] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[99404.114939] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[99404.114948] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current]
[99404.114953] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Incompatible medium installed
[99404.114960] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 e7 3f 80 00 00 08 00
[99404.114965] print_req_error: I/O error, dev sdb, sector 15155072
[99404.114975] Buffer I/O error on dev sdb, logical block 1894384, async page read
Indeed, you should see those 4 partitions on the chip when you connect it to Linux.The desoldered chip here was only cleaned, not reballed. It shows up under Linux as sdb1 2 3 and 4
Using an Allsocket SD adapter and a transcend usb3 SD reader
Allsocket set to 1.8V
Did you try a new emmc in your setup to format and read that to see if the setup is fine ?
Replacing my working Emmc because its just a 1:1 copy, no repair needed. If the chip goes bad, a repair might be complicatd, so its just 10min reading and 10min writing. New chip has better specs than the old one and will live longer
Sad Sack, be advised that replacing a cheaply-made chip with an industrial-grade one, is not comparable to replacing like-for-like.My 2 cents...
There's no point in premptively replacing the eMMC before it fails. Any replacement will fail eventually as well.
Is that something though, that a sensible engineer would recommend?Not necessarily: My Hynix chip was cleaned (all balls removed) with braid+hot air (not braid+solder iron!), and it could be read just fine in the programmer.