[anstr]

Hi All,

Could you help me understand how Secure Coding (S.C) will impact working on vehicles in future on Esys ?

What I understand from ISTA release notes and esys help section S.C. requires backend connection to AOS/Sgate in order to sign NCD’s. If we have such access then the process is automated with ISTA/Esys communicating automatically for signatures or manual upload via ticket. 

If I got the Release Notes correctly this is only applicable for I20 and newer builds. But here I’m missing clarity and got really confused.
 

1. Is the introduction of S.C. dependent on Esys/ISTA version or a certain PSDZdata level (for example 4.36.12) ?
   
2.  SecureCoding on S15A ? In Esys 3.40.2 I see a new option in TAL execution tab „Programming Tokens” and some more options in TAL list. According to documentation all ECU with avaiable option „ecuMirrorDeploy” require signing. Example from my TAL belo
   
3. Does anyone know what exactly  „ecuMirrorDeploy” „ecuPoll” and „ecuActivate" stand for (outside of self explanatory meanings)?
   
4. Are there any solutions overcoming S.C. or basically this means BMW AOS here we come ?
   
5. Looking at Esys Launcher 5 or Esys Ultra I can see that „SWL SEC” is showing as logged in – what does it mean and do ? I understand this is where you put your credentials in order to sign NCD’s.
   
6. Is CODING 2.0 just a different name for S.C. ?
   

Thank you for your help and clarification!

<[ATM2 - 61] finalizeECUMirrorFlash finished with error [PROGRESS]>
<[] Programming token is either empty or unsigned: empty: true, unsigned: true [THROWABLE]>

[st1]

I’m looking for same answers.
My car was updated G82 xDrive with 4.36.12 and VTG (LMV3 ECU in Esys) file CAFD I think requires signing and came with same error you have.
Problem also is AOS is lagging behind only on 4.35.42 as per picture so cannot do anything but wait for later software to come out…

[pillpusher84]

So, am i to understand that you now require a subscription to AOS in order to get the online CAFDs?

I see you are using ISTA, however does this mean that you can not code with ESYS with these online files? Is there any way to intercept these file and get them offline?

[anstr]

So, am i to understand that you now require a subscription to AOS in order to get the online CAFDs?

I see you are using ISTA, however does this mean that you can not code with ESYS with these online files?  Is there any way to intercept these file and get them offline?

In general seems that BMW wants to put stop to unauthorized coding activities and will control cafd and signing of files in their backend system connected to ISTA and Esys via credentials to AOS/S-gate. So far Esys Plus and Launcher 5 seem to have an idea for coding 2.0 solution, but I have not tested it

[ferbmw]

I’m looking for same answers.
My car was updated G82 xDrive with 4.36.12 and VTG (LMV3 ECU in Esys) file CAFD I think requires signing and came with same error you have.
Problem also is AOS is lagging behind only on 4.35.42 as per picture so cannot do anything but wait for later software to come out…

Does the warning appears during the measures plan calculation or AFTER the process has started? I am planning to update my G20 build date 11-2021 but after reading this and other posts I am refraining to flash.

[diagso]

I’m looking for same answers.
My car was updated G82 xDrive with 4.36.12 and VTG (LMV3 ECU in Esys) file CAFD I think requires signing and came with same error you have.
Problem also is AOS is lagging behind only on 4.35.42 as per picture so cannot do anything but wait for later software to come out…

Does the warning appears during the measures plan calculation or AFTER the process has started? I am planning to update my G20 build date 11-2021 but after reading this and other posts I am refraining to flash.

Read the ISTA Release Notes section on secure coding and token. Process is decribed there in details.

[st1]

Once is starts calculating measures plan, the error pops up and pressing retry, still same error.

[Node]

I don't know what these new ecuMirror, etc mean exactly, but from some experiments I've done on them this seems like a preparation for a new flashing sequence too. I don't think these are related to secure coding.

For now these can be avoided by unchecking "with Mirror-protocol" in TAL calculation. Then it calculates old style TAL which can be processed without any online source. As does ISTA, because I flashed G30 (which has DKOMBI with these new mirror things) with standalone ISTA without any issues.

Now what in my guess this means. For now all the units have necessary security keys in local data.
In the future, however, my guess is security keys for units also will not be distributed in the local data and will be generated online. Hence the json is made in generate token and then the keys need to be set in the other box.

[st1]

In Esys after calculating which ECUs are to be updated, Is there an easy way to establish which files including CAFs and BTLD require secure coding?

[LeonidLunin]

Cafd for coding 2.0 can be signed, pm if need