Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Manual firmware update (for new charge port)

This site may earn commission on affiliate links.
Sure, only the staged_update and gateway_needs_update have changed to no. The rest is same as before.

Executable: /bin/cid-updater, personality: cid-updater, hash <redacted>, built for package version: develop-2018.50.6-36-4ec03ed8fb
uptime: 1214.760799000s
/proc/uptime: 1232.33 4530.74
current bootdata Contents: 0xef 0xbe 0xad 0xde 0x01 0x00 0x00 0x00 0xff 0x00 0x1f 0xff 0xff 0xff 0xff 0xff 0x00 0x00 0x00 0x00 0x40 0x60 0x68 0x3d 0x78 0x30 0x36 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
Pattern: 0xdeadbeef
Online boot bank: KERNEL_A
Online fail count: 0
Online dot-model-s size: 0
Offline boot bank: KERNEL_B
Offline fail count: 31
Offline dot-model-s size: 1030250560
MCU Board Revision: x06
Fused: 1
Override-version: 0
Online map bank: BANK_A
Online map package size: 0
Online map signature: NULL
Offline map bank: BANK_B
Offline map package size: 0
Offline map signature: NULL
running_in_recovery_partition = 0
installed_firmware_signature = NULL
offline_firmware_signature = <redacted>
ic_installed_firmware_signature = NULL
ic_offline_firmware_signature = NULL
ape_installed_firmware_signature = NULL
ape_offline_firmware_signature = NULL
ape_installed_firmware_signature = NULL
ape_offline_firmware_signature = NULL
vin = <redacted>
staged_update = no
gateway_needs_update = no
updating_maps = no
END STATUS
 
Thank you, for all the information in this tread. There is not much I can add. I ordered the cable, but is arriving tomorrow. I lost patience and use a solid network cable that I just pushed in the car connector. I managed to break the copper and a piece stuck in the connector. Luckily I was able to pull it without damaging the connector too much. Car is now charging at 40A on the new port. Thanks again.
 
Hi guys. I have some problem with my cid. My cid is a black screen. I can't power on screen. But tegra3 work normal. Here are my logs. What do you think about my problem? Fall off FPGA (Altera)? Or problem in spi fw for FPGA Altera? I'm sorry if I wrote on a foreign topic.
Code:
root@cid-XXXXXXXXXXXXXXXXX# Write failed: Broken pipe
root@localhost:~#
root@localhost:~# ssh [email protected]
[email protected]'s password:
Linux cid 4.4.162-release-03mar2017-gca2e7d0-dirty #see_/etc/commit SMP PREEMPT 1202798460 armv7l armv7l armv7l GNU/Linux


Welcome to Ubuntu!
 * Documentation:  https://help.ubuntu.com/
Last login: Mon Feb 24 13:11:23 2020 from ic
tesla1@cid-XXXXXXXXXXXXXXXXX$ sudo su
root@cid-XXXXXXXXXXXXXXXXX# cat /var/log/syslog | grep displ
2020-02-24T11:17:15.107301-08:00 cid QtCar[753]: [] ERROR FPGA reports display error: ff
2020-02-24T11:17:42.987007-08:00 cid QtCar[753]: [] ERROR FPGA reports display error: ff
2020-02-24T11:18:09.416187-08:00 cid QtCar[753]: [] ERROR FPGA reports display error: ff
2020-02-24T11:18:35.746332-08:00 cid QtCar[753]: [] ERROR FPGA reports display error: ff
2020-02-24T11:18:52.425398-08:00 cid QtCar[753]: [PerfEventLogger] INFO display_state:0 drive_rail:0 gear:-1 autopilot:-1 map:1 net:                         0
-
-
2020-02-24T13:12:30.888869-08:00 cid QtCar[756]: [] ERROR FPGA reports display error: ff
2020-02-24T13:12:52.141233-08:00 cid QtCar[756]: [] ERROR FPGA reports display error: ff
2020-02-24T13:13:40.145262-08:00 cid QtCar[761]: [DisplayStateManager] INFO managing datavalue CD_displayState
2020-02-24T13:13:40.185287-08:00 cid QtCar[761]: [PerfEventLogger] INFO display_state:-1 drive_rail:0 gear:-1 autopilot:-1 map:0 net                         :-1
2020-02-24T13:13:41.158376-08:00 cid QtCar[761]: [PerfEventLogger] INFO display_state:2 drive_rail:0 gear:-1 autopilot:-1 map:0 net:                         -1
2020-02-24T13:13:43.233060-08:00 cid QtCar[761]: [] INFO InfoClassicDisplayHardwareManager FPGA: display power request  1
2020-02-24T13:13:43.233788-08:00 cid QtCar[761]: [PerfEventLogger] INFO display_state:2 drive_rail:0 gear:-1 autopilot:-1 map:0 net:                         -1
2020-02-24T13:13:43.980749-08:00 cid QtCarAudiod[862]: [AudioStateSX] INFO Setting entertainment mute false because CD_displayState                          2
2020-02-24T13:13:43.981051-08:00 cid QtCarMonitor[829]: [DataValueManager] INFO CD_displayState now '2' (was '<invalid>')
2020-02-24T13:13:54.316212-08:00 cid QtCarVehicle[834]: [ModelSVehicleLink] INFO UI ready, starting center display requests
2020-02-24T13:13:54.540664-08:00 cid QtCarVehicle[834]: [BodyControlsManager] INFO starting center display body requests
2020-02-24T13:13:54.846746-08:00 cid QtCar[761]: [NativeMaps::TileManager] INFO manageConnectivity internet: false display on true
2020-02-24T13:13:54.972919-08:00 cid QtCar[761]: [PerfEventLogger] INFO display_state:2 drive_rail:0 gear:-1 autopilot:-1 map:1 net:                         -1
2020-02-24T13:14:04.544807-08:00 cid QtCar[761]: [] ERROR FPGA reports display error: ff
2020-02-24T13:14:04.988389-08:00 cid QtCar[761]: [DisplayHardwareManager] INFO FPGA: GUI_displayHardwareOK = false , GUI_cameraHardw                         areOK = false
2020-02-24T13:14:11.001875-08:00 cid QtCar[761]: [PerfEventLogger] INFO display_state:2 drive_rail:0 gear:-1 autopilot:-1 map:1 net:                         0
2020-02-24T13:14:25.876783-08:00 cid QtCar[761]: [] ERROR FPGA reports display error: ff
-
-
[DisplayHardwareManager] INFO FPGA: GUI_displayHardwareOK = false , GUI_cameraHardw                         areOK = false
 
Hmm, it's unlikely that the FPGA has failed unless you've been tinkering with it. And it's coherent enough to report this:
Code:
INFO FPGA: GUI_displayHardwareOK = false , GUI_cameraHardw...

I think the problem is likely with the display screen. Is there any chance you unplugged it while powered up? Have you another screen to substitute?