DIY: F8x Software Update Tips

[TB///M3]

Originally Posted by aboulfad

YMMV, it all depends how perceptive to changes you are, some people claim miraculous transformations to their cars upon software update, I, on the other hand am more skeptical...

An OBD2 tune from select vendors will update the DME software to latest and provide you with a tune applied to that latest DME version. An Istep update to latest will update ALL applicable ECUs in your car.

You also have another option, as was detailed in my OP, update only certain ECUs, and you can have that done by a remote vendor (e.g. Alex@Alpine).

Thanks...Alex must be busy cause I have reached out to him, but his email response have been very slow.

[Alex@Alpine]

Originally Posted by TB///M3

Thanks...Alex must be busy cause I have reached out to him, but his email response have been very slow.

Very sorry, emails are backed up. Send me a text at 310-560-0808 or if you are international +13105600808. Thank you.

[pmooiweer]

Originally Posted by TB///M3

I don't plan to pay, but that 5 soft blinker is the best coding option for me as I can't stand only 3 blinks. You telling me the new update will remove that and can't be coded back?

Yup; coding of soft blinker no longer works after flashing to newer software versions.

[Deleted-User]

Originally Posted by Celestion

Right. My Rheingold production date changed from 10/2015 to 07/2015 after the euro flash. It appears that my zeitgeistheizeachtungklipsch has always been 07/2015 in E-SYS (which didn't realize was normal until seeing your post). So the only odd thing now is that my changed Rheingold date.

I'm having the same issue. Did you find a solution?

[Celestion]

Originally Posted by netinvader

I'm having the same issue. Did you find a solution?

Nope.... let me know if you figure it out though

[Steveo]

Is the Head unit, HU NBT the only module where IBADeploy is ticked in Esys, any other modules require this?

[shawnsheridan]

Originally Posted by Steveo

Is the Head unit, HU NBT the only module where IBADeploy is ticked in Esys, any other modules require this?

IBADeploy is only used for Head Units.

[Steveo]

Thanks Shawn.

[Almaretto]

Originally Posted by Steveo

Is the Head unit, HU NBT the only module where IBADeploy is ticked in Esys, any other modules require this?

That is for user manual. No other ECU can pull up.

[FBMWWINS]

Please help.

I flashed all ECUs on my F32 (built 05-2014) (including FEM_GW) with ESYS but there is one stubborn such as NBT_HU which won't let me update:

LOG:

Read SVT before TAL execution started.

TAL execution started.
ExecutionID=2018/09/27-22:42:09.424
[] prepareTALExecution started [PROGRESS]
[] prepareTALExecution finished [PROGRESS]
[] prepareVehicleForFlash started [PROGRESS]
[] prepareVehicleForFlash finished [PROGRESS]
[] SVK-Ist does not match expected SGBMIDs for ecu ECUId:HU_NBT_0x63. Excpected (relevant process classes only): [hwel_00002fc2-001_004_001], Actual (relevant process classes only): [hwel_00001295-001_021_021], Missing SGBMID(s): [hwel_00002fc2-001_004_001], Surplus SGBMID(s): [hwel_00001295-001_021_021] [THROWABLE]
[HU_NBT - 63] There was an error during TAL execution, please check the log files. [WARN]
[HU_NBT - 63] - [Exception - HU_NBT - 63] SVK-Ist does not match expected SGBMIDs for ecu ECUId:HU_NBT_0x63. Excpected (relevant process classes only): [hwel_00002fc2-001_004_001], Actual (relevant process classes only): [hwel_00001295-001_021_021], Missing SGBMID(s): [hwel_00002fc2-001_004_001], Surplus SGBMID(s): [hwel_00001295-001_021_021]
[HU_NBT - 63] installECUBL started [PROGRESS]
[HU_NBT - 63] installECUBL finished [PROGRESS]
[HU_NBT - 63] finalizeECUBLUpdate started [PROGRESS]
[HU_NBT - 63] finalizeECUBLUpdate finished [PROGRESS]
[] finalizeVehicleFlash started [PROGRESS]
[] finalizeVehicleFlash finished [PROGRESS]
[] prepareVehicleForCoding started [PROGRESS]
[] prepareVehicleForCoding finished [PROGRESS]
[] finalizeVehicleCoding started [PROGRESS]
[] finalizeVehicleCoding finished [PROGRESS]
[] finalizeTALExecution started [PROGRESS]
[] finalizeTALExecution finished [PROGRESS]
TAL execution finished [TAL_EXECUTION_FINISHED]
TAL-Execution finished with status: "FinishedWithError". [C207]
TAL execution finished. Duration: "3min 39s". [C206]

Read SVT after TAL execution started.
Read SVT after TAL execution finished.

ILevel shipment and target were:

I_Step SHIPMENT: F020-14-03-503
I-Step TARGET: F020-18-07-531


Before TAL calculation, this is how NBT_HU looks here:

https://ibb.co/btHDbp


There are a couple of BLUE entries showing ACTUAL STATE but nothing red! So no identifiable target state there. Funny thing after calculating TAL and then going to processing it will no longer show up:


https://ibb.co/hqytcU


Open for any suggestions and feel kind of lost now.

[shawnsheridan]

Originally Posted by F06WINS

Please help.

I flashed all ECUs on my F32 (built 05-2014) (including FEM_GW) with ESYS but there is one stubborn such as NBT_HU which won't let me update:

LOG:

Read SVT before TAL execution started.

TAL execution started.
ExecutionID=2018/09/27-22:42:09.424
[] prepareTALExecution started [PROGRESS]
[] prepareTALExecution finished [PROGRESS]
[] prepareVehicleForFlash started [PROGRESS]
[] prepareVehicleForFlash finished [PROGRESS]
[] SVK-Ist does not match expected SGBMIDs for ecu ECUId:HU_NBT_0x63. Excpected (relevant process classes only): [hwel_00002fc2-001_004_001], Actual (relevant process classes only): [hwel_00001295-001_021_021], Missing SGBMID(s): [hwel_00002fc2-001_004_001], Surplus SGBMID(s): [hwel_00001295-001_021_021] [THROWABLE]
[HU_NBT - 63] There was an error during TAL execution, please check the log files. [WARN]
[HU_NBT - 63] - [Exception - HU_NBT - 63] SVK-Ist does not match expected SGBMIDs for ecu ECUId:HU_NBT_0x63. Excpected (relevant process classes only): [hwel_00002fc2-001_004_001], Actual (relevant process classes only): [hwel_00001295-001_021_021], Missing SGBMID(s): [hwel_00002fc2-001_004_001], Surplus SGBMID(s): [hwel_00001295-001_021_021]
[HU_NBT - 63] installECUBL started [PROGRESS]
[HU_NBT - 63] installECUBL finished [PROGRESS]
[HU_NBT - 63] finalizeECUBLUpdate started [PROGRESS]
[HU_NBT - 63] finalizeECUBLUpdate finished [PROGRESS]
[] finalizeVehicleFlash started [PROGRESS]
[] finalizeVehicleFlash finished [PROGRESS]
[] prepareVehicleForCoding started [PROGRESS]
[] prepareVehicleForCoding finished [PROGRESS]
[] finalizeVehicleCoding started [PROGRESS]
[] finalizeVehicleCoding finished [PROGRESS]
[] finalizeTALExecution started [PROGRESS]
[] finalizeTALExecution finished [PROGRESS]
TAL execution finished [TAL_EXECUTION_FINISHED]
TAL-Execution finished with status: "FinishedWithError". [C207]
TAL execution finished. Duration: "3min 39s". [C206]

Read SVT after TAL execution started.
Read SVT after TAL execution finished.

ILevel shipment and target were:

I_Step SHIPMENT: F020-14-03-503
I-Step TARGET: F020-18-07-531

Before TAL calculation, this is how NBT_HU looks here:

https://ibb.co/btHDbp

There are a couple of BLUE entries showing ACTUAL STATE but nothing red! So no identifiable target state there. Funny thing after calculating TAL and then going to processing it will no longer show up:

https://ibb.co/hqytcU

Open for any suggestions and feel kind of lost now.

I have replied to your multiple PM's regarding this. You still have FA / SVT issues.

"SVK-Ist does not match expected SGBMIDs for ecu ECUId:HU_NBT_0x63" meaning HWEL in svt_soll is not Black as I advised it MUST be.

[FBMWWINS]

Hallo Shawn,

I appreciate that but this printscreen of the HU_NBT ECU is taken after calculating SVT_SOLL:

https://ibb.co/btHDbp


As you can see HWEL is black. Yet now when calculating TAL, this ECU does not even show up anymore.

I managed to successfully update all other ones clearly it escapes me where or what I am doing wrong.

[shawnsheridan]

Originally Posted by F06WINS

Hallo Shawn,

I appreciate that but this printscreen of the HU_NBT ECU is taken after calculating SVT_SOLL:

https://ibb.co/btHDbp


As you can see HWEL is black. Yet now when calculating TAL, this ECU does not even show up anymore.

I managed to successfully update all other ones clearly it escapes me where or what I am doing wrong.

I have no idea when the picture was taken related to the condition of car when actual TAL files were created and run. Maybe something has changed between the two. What is clear though based on the TAL error you posted, is that there is SVT error, and that is indisputable.

Incidentally, that picture shows an ECU without any updates, as in nothing to even Flash. It has no Red targets.

[FBMWWINS]

Thanks.

As said I took the printscreen just after calculating SVT_SOLL. No doubt there is an SVT error I never disputed that. I see there is no target value and only the 2 blue ones (actual state).

After the latest TAL calculation procedue it looks as follows:

https://ibb.co/hqytcU


Perhaps I should try ZBE3 now - takes only 3-4 minutes usually.

[Almaretto]

Originally Posted by F06WINS

Funny thing after calculating TAL and then going to processing it will no longer show up:

That is how it should be. If there is no SVTarget, why would there be option to update?

[FBMWWINS]

Hallo and thanks for this input.
I was wondering then why there are those 2 blue positions whereas all other ECUs not requiring updates are all black. I had seen a mix of blue and red (actual vs. target) but never like this just blue. NBT_HU was last updated (with rest of the ECUs) a while ago (almost 2 years) - back then by BMW themselves.

[Almaretto]

Originally Posted by F06WINS

Hallo and thanks for this input.
I was wondering then why there are those 2 blue positions whereas all other ECUs not requiring updates are all black. I had seen a mix of blue and red (actual vs. target) but never like this just blue. NBT_HU was last updated (with rest of the ECUs) a while ago (almost 2 years) - back then by BMW themselves.

Black means SVTactual = SVTarget. It has been over 2 years since NBT2 was released. Sometimes there are no updates for older ECU's.

[FBMWWINS]

It is NBT NEXT (thus HU_NBT) and not NBT2. I refer to the F32 car (built 05-2014) and still featuring the original factory fitted Headunit.

[Almaretto]

Originally Posted by F06WINS

It is NBT NEXT (thus HU_NBT) and not NBT2. I refer to the F32 car (built 05-2014) and still featuring the original factory fitted Headunit.

I know. My answer still is the same.

[FBMWWINS]

Ok get it now if NBT2 has not received any updates for 2 years (and it is newer...) then my NBT (last updated 2 years ago by my BMW dealer) could present the same scenario thus not feature anything new for the same past amount of time.

[Almaretto]

Originally Posted by F06WINS

Ok get it now if NBT2 has not received any updates for 2 years (and it is newer...) then my NBT (last updated 2 years ago by my BMW dealer) could present the same scenario thus not feature anything new for the same past amount of time.

Close. NBT2 has seen updates. NBT, an older module, may not.

[baturbo]

Should I be worried