Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]
Secure Coding: impact on Esys
09-07-2022, 19:21 PM,
Post: #1
|
|||
|
|||
Secure Coding: impact on Esys
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.
<[ATM2 - 61] finalizeECUMirrorFlash finished with error [PROGRESS]> <[] Programming token is either empty or unsigned: empty: true, unsigned: true [THROWABLE]> |
|||
10-07-2022, 12:16 PM,
Post: #2
|
|||
|
|||
RE: Secure Coding: impact on Esys
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… |
|||
10-07-2022, 14:31 PM,
Post: #3
|
|||
|
|||
RE: Secure Coding: impact on Esys
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? |
|||
10-07-2022, 18:18 PM,
Post: #4
|
|||
|
|||
RE: Secure Coding: impact on Esys
(10-07-2022, 14:31 PM)pillpusher84 Wrote: So, am i to understand that you now require a subscription to AOS in order to get the online CAFDs? 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 |
|||
10-07-2022, 23:05 PM,
Post: #5
|
|||
|
|||
RE: Secure Coding: impact on Esys
(10-07-2022, 12:16 PM)st1 Wrote: I’m looking for same answers. 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. |
|||
11-07-2022, 07:21 AM,
Post: #6
|
|||
|
|||
RE: Secure Coding: impact on Esys
(10-07-2022, 23:05 PM)ferbmw Wrote:(10-07-2022, 12:16 PM)st1 Wrote: I’m looking for same answers. Read the ISTA Release Notes section on secure coding and token. Process is decribed there in details. |
|||
11-07-2022, 11:47 AM,
Post: #7
|
|||
|
|||
RE: Secure Coding: impact on Esys
Once is starts calculating measures plan, the error pops up and pressing retry, still same error.
|
|||
17-07-2022, 08:40 AM,
Post: #8
|
|||
|
|||
RE: Secure Coding: impact on Esys
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. |
|||
Reputation: +1 - anstr [+1] | |||
27-07-2022, 17:49 PM,
Post: #9
|
|||
|
|||
RE: Secure Coding: impact on Esys
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?
|
|||
27-06-2023, 01:36 AM,
Post: #10
|
|||
|
|||
RE: Secure Coding: impact on Esys
Cafd for coding 2.0 can be signed, pm if need
|
|||
Reputation: +1 - foxportal [+1] | |||
« Next Oldest | Next Newest »
|
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Return to TopReturn to Content