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

Firmware 8.0

This site may earn commission on affiliate links.
I "dislike" the content of this message. :(
(Gently O/T:))
We DO need a button that says: "I agree", rather than "Dislike" as I often want to agree with a post that is about a topic that makes us sad: if you use "dislike", it says: "I dislike your post"
but in fact I want to say
"your post is valid and useful, but yes, what you say is true and I agree I don't like it"
 
Last edited:
I doubt they are holding release for such things.

Correct. They wouldn't halt rollout and pull the uninstalled, staged update from cars if it didn't cause some problem along the lines of:
- failed installation that requires service center action
- safety feature, such as a specific range of radar serial numbers going offline from the firmware change
- operability function, such as drive unit being limited or blowing a contactor fuse
 
So on the one car I installed on, it had some difficulty with the DAS and Parking Brake ECU:
Code:
Update gtw.hex 0xc6bb24d2 => 0x2098ceeb   succeeded.
Update bms.hex 0x41cf045e => 0xd16e36ac   succeeded.
Update chgvi.hex 0x4b8a302f => 0xcd930262   succeeded.
Update chgsvi.hex 0x4b8a302f => 0xcd930262   succeeded.
Update cp.hex 0xf026bc72 => 0xbbcfe633   succeeded.
Update di.hex 0x25b7aafc => 0x8929aee5   succeeded.
Update dis.hex 0x5ac51e02 => 0x3c7ac1b7   succeeded.
Update pm.hex 0x950365e9 => 0x75b73dad   succeeded.
Update pms.hex 0xf97f0c50 => 0x75e7894f   succeeded.
Update thc.hex 0xa9a95fba => 0x54f19ddd   succeeded.
Update das.bhx 0x6a73b5af => 0x5c1b4f99   succeeded.
Update dasmeapp.bhx 0x71375409 => 0xa035dda2   failed.
Update dasmeffs.bhx 0xdc33faba => 0x7e502d43   failed.
Update park.hex 16.8.55 => 16.8.58   failed.
Update dsp.hex succeeded.
Update epb.hex 0xda8531ec => 0x0829438a   succeeded.
Update radc.bhx 0x98fd09d0 => 0x0f813f1c   succeeded.
Update ibst.bhx 0xbde54ddf => 0xca4b6c9e   succeeded.
Update ibstcal.hex succeeded.
Update sec.hex 21.2.0 => 21.3.0   succeeded.

Retrying... (1 of 4)

Update dasmeapp.bhx 0x71375409 => 0xa035dda2   succeeded.
Update dasmeffs.bhx 0xdc33faba => 0x7e502d43   succeeded.
Update park.hex 16.8.55 => 16.8.58   succeeded.
Overall result: succeeded.
I've seen stuff like this before, but this release is tricky on that if it fails on a car with older than 2.36.x, It cannot be rolled back. I don't think this is the issue, but it's worth noting.
 
You don't need internet to install once it's staged. But yeah, I think I'd drive home and make sure they don't yank it later. They'll be sending out a new version soon that fixes whatever they found to halt the rollout.
I like to be home and connected when I install updates just in case something goes wrong and Tesla needs to connect and diagnose. And in this case, I'm assuming I would need Internet for Tesla to tell my car to cancel the update.

I've been home for about 45 minutes now and my car still shows an update available, but I'm still postponing it. Do we know how the withdrawing of updates presents itself? Would the alarm clock icon disappear? Or would I have to try to start the update and it would then say "nope, sorry, that update is no longer available?"
 
The clock disappears. It happened to my 70D a few updates ago when there was an issue.

I like to be home and connected when I install updates just in case something goes wrong and Tesla needs to connect and diagnose. And in this case, I'm assuming I would need Internet for Tesla to tell my car to cancel the update.

I've been home for about 45 minutes now and my car still shows an update available, but I'm still postponing it. Do we know how the withdrawing of updates presents itself? Would the alarm clock icon disappear? Or would I have to try to start the update and it would then say "nope, sorry, that update is no longer available?"
 
So on the one car I installed on, it had some difficulty with the DAS and Parking Brake ECU:
Code:
Update gtw.hex 0xc6bb24d2 => 0x2098ceeb   succeeded.
Update bms.hex 0x41cf045e => 0xd16e36ac   succeeded.
Update chgvi.hex 0x4b8a302f => 0xcd930262   succeeded.
Update chgsvi.hex 0x4b8a302f => 0xcd930262   succeeded.
Update cp.hex 0xf026bc72 => 0xbbcfe633   succeeded.
Update di.hex 0x25b7aafc => 0x8929aee5   succeeded.
Update dis.hex 0x5ac51e02 => 0x3c7ac1b7   succeeded.
Update pm.hex 0x950365e9 => 0x75b73dad   succeeded.
Update pms.hex 0xf97f0c50 => 0x75e7894f   succeeded.
Update thc.hex 0xa9a95fba => 0x54f19ddd   succeeded.
Update das.bhx 0x6a73b5af => 0x5c1b4f99   succeeded.
Update dasmeapp.bhx 0x71375409 => 0xa035dda2   failed.
Update dasmeffs.bhx 0xdc33faba => 0x7e502d43   failed.
Update park.hex 16.8.55 => 16.8.58   failed.
Update dsp.hex succeeded.
Update epb.hex 0xda8531ec => 0x0829438a   succeeded.
Update radc.bhx 0x98fd09d0 => 0x0f813f1c   succeeded.
Update ibst.bhx 0xbde54ddf => 0xca4b6c9e   succeeded.
Update ibstcal.hex succeeded.
Update sec.hex 21.2.0 => 21.3.0   succeeded.

Retrying... (1 of 4)

Update dasmeapp.bhx 0x71375409 => 0xa035dda2   succeeded.
Update dasmeffs.bhx 0xdc33faba => 0x7e502d43   succeeded.
Update park.hex 16.8.55 => 16.8.58   succeeded.
Overall result: succeeded.
I've seen stuff like this before, but this release is tricky on that if it fails on a car with older than 2.36.x, It cannot be rolled back. I don't think this is the issue, but it's worth noting.

What is the function of the DAS, and why might these errors occur?
 
Correct. They wouldn't halt rollout and pull the uninstalled, staged update from cars if it didn't cause some problem along the lines of:
- failed installation that requires service center action
- safety feature, such as a specific range of radar serial numbers going offline from the firmware change
- operability function, such as drive unit being limited or blowing a contactor fuse
Agreed. I trust Tesla will do the right thing, so I'm not worried with that. As much as Elon has successfully gotten everyone excited about 8.0, I'd rather have a delay than keep pushing something out that has the potential of creating a major issue for owners and the brand. I would hope all owners would be of the same opinion.

...but as a guy who has run some large business critical rollouts and migrations, it does make we wonder how a potentially big failure that stops a global rollout got through -- if the cross-section of NDA'd testers (especially if there are 700+ of them as some have said) is representative enough of the growing fleet diversity, and Tesla's expectations of, and feedback from those testers is considered sufficiently in advance of a GO decision. Assuming that's what has happened, its a big deal to have something pulled and corrected at this late phase. We'll likely never know any facts, but I'm glad I'm not inside Tesla and downstream of Elon right now. Heads will be rolling.
 
Last edited:
:D

2016-09-22_19.37.03.jpg
 
  • Like
Reactions: newtman
Alarm clock is still there on my screen. Car is currently in a parking garage with 1 bar of LTE. I'm not going to start the install here, don't want to risk getting stranded if something goes haywire. In about half an hour I'll be at home connected to my WiFi and plugged in. Given Ingineer's concerns I think I'll wait an hour or two to see if the staged update gets yanked off then.

I don't know how tesla handles their image management, but I can take an educated guess that they are signed, and the first step of the installer is to validate that signature. If you want to stop people from installing an image that has already been downloaded, you revoke the signature.

This will have the side effect that your car will still show the clock icon, but when you go to install the update it will state some kind of error and delete the image. At this point I would expect the clock icon to disappear.

It's also possible that the process that periodically checks for updates also checks the signature of a staged image, in which case the clock would just disappear.
 
Last edited:
  • Informative
Reactions: NikeWings