HowTo Tesla - Repairing the Black MCU Screen
So, I am now locked out of my CID, and all streaming radio is just static as are turn signals and all bongs. I thought Tesla had done it. But someone who would know told me they had never heard of Tesla doing this, and that it's more likely that Ingineer (Phil) has done this to me. It's a serious problem.
Ok so I appealed for help from some old friends: ce2078, verygreen, and appleguru. We used to share information. But for some reason each in his turn has gone into radio silence.
None will help me with this. No idea why. I am alone.
I notice that even with my repeated encouragement none of them has posted any sort of howto like the ones I've posted here. So it seems that this is what we are doing -- not helping anyone.
As a result I've taken down my howtos. I'm sorry about this but there is some kind of political problem which I don't understand.
Of course this action will not make any of them more likely to help me, I am sure quite the opposite. But at this point I have nothing to lose. Why should I help others when NO ONE will help me in an emergency? Life in the Big City.
Ok so I appealed for help from some old friends: ce2078, verygreen, and appleguru. We used to share information. But for some reason each in his turn has gone into radio silence.
None will help me with this. No idea why. I am alone.
I notice that even with my repeated encouragement none of them has posted any sort of howto like the ones I've posted here. So it seems that this is what we are doing -- not helping anyone.
As a result I've taken down my howtos. I'm sorry about this but there is some kind of political problem which I don't understand.
Of course this action will not make any of them more likely to help me, I am sure quite the opposite. But at this point I have nothing to lose. Why should I help others when NO ONE will help me in an emergency? Life in the Big City.
1 - 20 of 63 Posts
Thank you for this valuable info. However I am curious about just disabling logging to avoid disassembling a (for now) working mcu. It seems it would be easier to put the tegra into apx mode and use nvFlash to fix the firmware. I wonder if this can be done via Ethernet or somehow via the car's built in Wi-Fi..
Joined
·
2 Posts
@Quantum - Great post, great insight into the Tesla system. Wish it were more open (especially the audio system UI, which I hate and would love to rewrite).
I checked the TMC forum for posts by Quantum --- didn't find any. What username do you post under?
I checked the TMC forum for posts by Quantum --- didn't find any. What username do you post under?
Great content! Thanks everyone for sharing.
Correct me if I'm wrong but even though IC and CID eMMC partitions are not the same per-se, they both contain the car specific files right? So one theoretically could;
- Take out the p3 & p4 of any other car (which have the correct file system and complete files) Say it is /randomcid for example purposes
- Take their own IC p3 & p4 images (which have the car specific files) Say it is /myic for example purposes
- Extract them all on linux on separate directories
- use rsync -a /randomcid /myic
so it copies everything and still keeps car specific files.
Then you can use gparted to recreate p3 & p4 extfs3 partitions. Put them back on to an eMMC with p1&p2 partitions you can find which have to be the same version as Spansion.
Bob's your uncle! No?
Correct me if I'm wrong but even though IC and CID eMMC partitions are not the same per-se, they both contain the car specific files right? So one theoretically could;
- Take out the p3 & p4 of any other car (which have the correct file system and complete files) Say it is /randomcid for example purposes
- Take their own IC p3 & p4 images (which have the car specific files) Say it is /myic for example purposes
- Extract them all on linux on separate directories
- use rsync -a /randomcid /myic
so it copies everything and still keeps car specific files.
Then you can use gparted to recreate p3 & p4 extfs3 partitions. Put them back on to an eMMC with p1&p2 partitions you can find which have to be the same version as Spansion.
Bob's your uncle! No?
/var and /home partitions can be empty. Tesla will re-create everything you need on first boot.I've never needed to look at files on the IC, but have heard that some things are different. /var may be close enough, Idk.
Only /var (mmcblk0p3) is likely to ever be damaged as that's what gets hammered by Tesla's (justified) logging. But /var holds some mighty crucial files. This is why you should always try and dump the chip before it fails... and rest assured cowboys, it will fail.
rsync -a will check CRC of source and destination files, and then overwrite the destination files which don't match with the source ones. I'll bet that there is a switch which will preserve existing destination files, although that would preserve also the damaged ones. My best idea is to just pick through the custom files one-by-one, and then search for any straggling VINs, names, birthdays, etc with:
# grep -r "{vinlastfive}" /dev/mmcblk0p3
{hehe} Hey, I'm a "Junior Member" here!Little do they know I'm 64.
I did it myself. Was not able to recover any data from my MCU, so I copied mmc from IC, then wiped /var and /home partitions, extended /home partition and tesla created everything on first boot.
Edit:
almost everything.
I see this message in syslog:
2019-02-23T09:48:19.841473-08:00 cid QtCarNetManager[2451]: [SierraCellModem] INFO Cannot open /home/tesla/.Tesla/car/cell_apn
Anybody know the content of this file?
Thanks. I see no error message in the logs, but mobile internet does not work anyway. Probably cause of it US tesla in Europe. Have to replace sim card.
I see some other errors in the logs. Apart from it, everything seems to work as expected. Don't know if I should worry about it.
Code:
2019-02-24T15:03:14.236923-08:00 cid QtCarVehicle[613]: [ServiceDataListenManager] INFO created ServiceDataListenManager TMServer : 4401 frequency: high
2019-02-24T15:03:14.284608-08:00 cid QtCarVehicle[613]: [ServiceDataListenManager] INFO Now listening for data broadcasts from service TMServer on port 4401 (all interfaces)
2019-02-24T15:03:21.884562-08:00 cid QtCar[869]: [ServiceDataListenManager] INFO created ServiceDataListenManager TMServer : 4401 frequency: high
2019-02-24T15:03:21.886510-08:00 cid QtCar[869]: [ServiceDataListenManager] INFO Now listening for data broadcasts from service TMServer on port 4401 (all interfaces)
2019-02-24T15:03:44.729614-08:00 cid QtCarNetManager[1932]: [ServiceDataListenManager] INFO created ServiceDataListenManager TMServer : 4401 frequency: high
2019-02-24T15:03:44.755770-08:00 cid QtCarNetManager[1932]: [ServiceDataListenManager] INFO Now listening for data broadcasts from service TMServer on port 4401 (all interfaces)
2019-02-24T15:03:45.787778-08:00 cid QtCarGpsManager[1938]: [ServiceDataListenManager] INFO created ServiceDataListenManager TMServer : 4401 frequency: high
2019-02-24T15:03:45.799184-08:00 cid QtCarGpsManager[1938]: [ServiceDataListenManager] INFO Now listening for data broadcasts from service TMServer on port 4401 (all interfaces)
2019-02-24T15:03:46.012725-08:00 cid QtCarServer[1927]: [ServiceDataListenManager] INFO created ServiceDataListenManager TMServer : 4401 frequency: high
2019-02-24T15:03:46.069373-08:00 cid QtCarServer[1927]: [ServiceDataListenManager] INFO Now listening for data broadcasts from service TMServer on port 4401 (all interfaces)
2019-02-24T15:03:49.894553-08:00 cid qtcar-tmserver: QtCarTMServer starting
2019-02-24T15:03:50.770327-08:00 cid qtcar-tmserver: QtCarTMServer has stopped
2019-02-24T15:04:29.979760-08:00 cid QtCarServer[1927]: [ServiceTransportPool] ERROR Unable to connect to TMServer at [] 192.168.90.100:4400 within 50 msecs
2019-02-24T15:04:47.206514-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 1 repeated instances of [ServiceTransportPool] ERROR Unable to connect to TMServer at [] 192.168.90.100:4400 within 50 msecs
2019-02-24T15:05:47.206126-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 3 repeated instances of [ServiceTransportPool] ERROR Unable to connect to TMServer at [] 192.168.90.100:4400 within 50 msecs
2019-02-24T15:51:48.469502-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to TMServer at [] 192.168.90.100:4400 within 50 msecs
2019-02-24T15:51:48.469667-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to Horizon at [] 192.168.90.100:4180 within 50 msecs
2019-02-24T15:51:48.470222-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to EbServerIC at [ic] 192.168.90.101:4304 within 50 msecs
2019-02-24T15:51:48.470606-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to GpsDasDebug at [] 192.168.90.100:4162 within 50 msecs
2019-02-24T15:51:48.470980-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to EbServer at [] 192.168.90.100:4104 within 50 msecs
2019-02-24T15:51:48.472474-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to Media at [] 192.168.90.100:4145 within 50 msecs
2019-02-24T15:51:48.472951-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to ICSystemInfo at [ic] 192.168.90.101:0 within 50 msecs
2019-02-24T15:51:48.475396-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to ICNavServer at [ic] 192.168.90.101:4300 within 50 msecs
2019-02-24T15:51:48.475831-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to ICMapState at [ic] 192.168.90.101:4050 within 50 msecs
2019-02-24T15:51:48.476403-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to NavServer at [ic] 192.168.90.101:4200 within 50 msecs
2019-02-24T15:51:48.476903-08:00 cid QtCarServer[1927]: [LogAggregator] INFO 2 repeated instances of [ServiceTransportPool] ERROR Unable to connect to VehicleVolatile at [] 192.168.90.100:0 within 50 msecs
Code:
2019-02-24T15:50:30.633320-08:00 cid QtCarAudiod[637]: [] WARN ASSERTION FAILED Starting timer outside of owner thread! at ../../../utils/TimerAudit.cpp:25
2019-02-24T15:50:30.672629-08:00 cid QtCar[869]: [] WARN ASSERTION FAILED Starting timer outside of owner thread! at ../../../utils/TimerAudit.cpp:25
Joined
·
88 Posts
Oh great work you actually did it?! How though? I don't understand. I thought keys, shadow, vpn, VIN, mileage and every other car specific crucial info was on p3 & p4. So if you take dump of IC and just keep p1&2 and delete the contents of p3&p4 on a blank new MCU eMMC where does it get the data from?
I have a backup of another car's full eMMC dump but I guess if I do that then app access would be lost alongside VIN, mileage and VPN info. Could someone explain the files and their workings?
While having a bigger eMMC like 64GB instead of 8GB will give you an approx 8x life span, there is even a better way (IMHO) to increase the lifespan of an eMMC device by 10x. (Any modern eMMC device should support it)
You'd need the spec from
https://www.jedec.org/system/files/docs/JESD84-A441.pdf
(free to download after registration)
This describes a feature called 'Partitions - item 7.2.3, and what needs to be configured is the 'Enhanced User Data Area' (one time irreversible operation)
That will reduce the effective size by half, but it will transition the chip in a PseudoSLC mode, and yield a 10x lifespan. Chip will not wear out anymore, so a 64GB eMMC will become 32GB with a 40x lifespan. Car will be scrap before this eMMC device fails.
You'd need the spec from
https://www.jedec.org/system/files/docs/JESD84-A441.pdf
(free to download after registration)
This describes a feature called 'Partitions - item 7.2.3, and what needs to be configured is the 'Enhanced User Data Area' (one time irreversible operation)
That will reduce the effective size by half, but it will transition the chip in a PseudoSLC mode, and yield a 10x lifespan. Chip will not wear out anymore, so a 64GB eMMC will become 32GB with a 40x lifespan. Car will be scrap before this eMMC device fails.
1 - 20 of 63 Posts
