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, I know that possibility for EU citizens.
Banjo, did Micro-com tell you to have experiences with the similar situation (p3 contains only zeros) and still had managed to recover the keys from the chip?
The bench PSU has +ve, -ve and GND terminals - do I connect the ISP’s D0, CMD and CLK points to the relevant pads on the Tegra, along with +ve from the PSU (to the 2.8V pad), and then connect -ve on the PSU, GND on the PSU, GND pad on the board and GND on the ISP all together?
Many thanks - have now tried every which way but can't get the easyjtag plus with ISP to read the emmc, CMD timeout error continously. I know @LuckyLuke has got it to work with this hardware (and has been really helpful in trying to diagnose the issue for me) - has anybody else and is willing to share their setup? @Slexs, or did you end up using something else?If you don't know your equipment you should check with voltage meter before.
I would expect the adjusted voltage between V+ and V-, on most PSU's GND is earth and suitable to connect your antistatic mat/wristband - so you can forget GND and interconnect V-.
I just ran into the very same issue. p1 and p2 seem fine (they pass fsck) but getting squashfs errors and MCU refuses to come up. Did you resolve this?Tried the MCU with p1 and p2 restored and p3 and p4 empty save for apn-file and folders. MCU did not start up, tried the steering wheel reboot methods a couple of times. Desoldered the new emmc again today to verify i didn't damage it while soldering it. It was fine. Read the syslog file created on p3 which contained over a million lines of squashfs read errors. Turns out that p1/p2 wasn't ok after all. Unsquashfs confirms that they are toast (i should have tried this before..).
Any ideas on getting MCU operational without intact p1/p2?
You can use as small as 8GB chip, which should be cheaper, even in Swissbit line. Also, it's a standard eMMC interface so any BGA153 eMMC 4.0 or 5.0 should work (Tesla doesn't officially support swapping, so you take a risk, however small, trying a part nobody else has tried before). Is it really worth your time however to look for cheaper one and trying it, vs. using something you know has worked for others? Also, cheaper (and smaller) chips will give you lower expected lifetime (and therefore faster deterioration of performance). I guess only you can decide whether it's worth that. For me I went with Swissbit EM-26 32GB - highest reliability and performance part I could find, which is more than $58CAD (it costed me ~$70 USD), but that's because I wanted a solution so that I never have to worry about changing emmc chip again. Switching emmc chips is a lot of effort, and saving $30 is not worth to me having to have to do it again.Is there more affordable emmc chip? The Swiss bit is pretty expensive, 58CAD per chip.
If you don't keep it in reset, it's not the modified files you have to worry about, it's generally the bus contention by you and the MC accessing the bus a the same time.Is there any way to keep MC in reset mode, to make sure, no files will be altered during read/write?
I haven't seen this mentioned here before, what version of firmware was on it prior to removing it?I desoldered the emmc. Putting it easyjtag. It says emmc password locked. Is this normal to everyone? Mine is mcu1 from 2013 model s
It’s on 2019.40.2.3I haven't seen this mentioned here before, what version of firmware was on it prior to removing it?
That's an old version, no reported password locking. I was worried that maybe Tesla reacted to the recent media coverage of personal information leaks by finding some way to lock the emmc with a password, but for that version, you should be able to just read it. Not sure what makes EasyJTAG say the emmc is password locked. Are you sure you're trying to read the main MLC partition, and not RPMB or boot ones?It’s on 2019.40.2.3
I desoldered the emmc so the it should be isolated. the chip is h26m42001fmr. You just reminded me that i did brought my car to the service center for a quote on the repair. i don't think they did anything to lock the emmc though.That's an old version, no reported password locking. I was worried that maybe Tesla reacted to the recent media coverage of personal information leaks by finding some way to lock the emmc with a password, but for that version, you should be able to just read it. Not sure what makes EasyJTAG say the emmc is password locked. Are you sure you're trying to read the main MLC partition, and not RPMB or boot ones?
I desoldered the emmc so the it should be isolated. the chip is h26m42001fmr. You just reminded me that i did brought my car to the service center for a quote on the repair. i don't think they did anything to lock the emmc though.