BMW Forum - BimmerFest BMW Forums banner

Tv module coding failure

9K views 67 replies 8 participants last post by  shawnsheridan  
#1 ·
Okay, so I changed out my dvb-t tv-module to a dvb-t2, so I, and the kids, can watch TV in the car.

I swapped it over and tried my luck to see if it worked. I'd didn't. I scanned for Channels and now it found several digital channels, but it says no signal.

I expected that, and went to esys (not launcher) to code it.

I detected Cafe for swe and coded it with success.

Same story, finds channels, but says no signal.

Okay, so I wanted to flash to same ilevel as the car.

I read vcm (I later tried read ecu), hw I'd from actual, calculated tal and so on.

Had the option to flash the TV module and proceeded.

It ended with failure. But why? What went wrong? I think it was the same story with an other TV module I tried 1 year ago ( it was the wrong non digital anyways, so I stopped after 1 attempt).

I have inserted the log. Any inputs are welcome.

I have Inserted pictures as well.

LOG:

Read SVT before TAL execution started.

TAL execution started.

ExecutionID=2022/03/25-19:05:12.265

[] prepareTALExecution started [PROGRESS]

[] prepareTALExecution finished [PROGRESS]

[] prepareVehicleForFlash started [PROGRESS]

[] prepareVehicleForFlash finished [PROGRESS]

[TV_MODUL - 4B] prepareECUforBLUpdate started [PROGRESS]

[TV_MODUL - 4B] prepareECUforBLUpdate finished [PROGRESS]

[TV_MODUL - 4B] authenticateECUforBLUpdate started [PROGRESS]

[TV_MODUL - 4B] authenticateECUforBLUpdate finished [PROGRESS]

[TV_MODUL - 4B - flsl_0000050c-005_000_027] Transaction type: blFlash; Message: TA started [TRANSACTION]

[TV_MODUL - 4B] performECUBLUpdate started with protocol UDS [PROGRESS]

MCDDiagService<id=56634, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUFlashBL, service=RC_EM_IE - RoutineControl EraseMemory IndicatedErasing, description=error: negative response : conditionsNotCorrect, link=TV_MODUL_4B_ETHERNET> [DIAGSERVICE]

[TV_MODUL - 4B - flsl_0000050c-005_000_027] Transaction type: blFlash; Message: 0% progress on ECUId:TV_MODUL_0x4B [0% of flsl_0000050c-005_000_027] [TRANSACTION]

[] job failed with negative response error:

code: repeat job

description: Service RC_EM_IE returned a negative response with response code conditionsNotCorrect; LinkName: TV_MODUL_4B_ETHERNET

severity: ERROR

[THROWABLE]

[TV_MODUL - 4B - flsl_0000050c-005_000_027] Transaction type: blFlash; Message: TA finished [TRANSACTION]

[TV_MODUL - 4B] -MessageID is used multiple times, so MessageText may be ambiguous-job failed with negative response error:

code: repeat job

description: Service RC_EM_IE returned a negative response with response code conditionsNotCorrect; LinkName: TV_MODUL_4B_ETHERNET

severity: ERROR

[WARN]

[TV_MODUL - 4B] - [Exception - TV_MODUL - 4b] job failed with negative response error:

code: repeat job

description: Service RC_EM_IE returned a negative response with response code conditionsNotCorrect; LinkName: TV_MODUL_4B_ETHERNET

severity: ERROR

[TV_MODUL - 4B] prepareECUforBLUpdate started [PROGRESS]

MCDDiagService<id=230634, job=com.bmw.psdz.jobs.uds.MCD3_PrepareECUforBLUpdate, service=DSC - DiagnosticSessionControl, description=error: negative response : conditionsNotCorrect, link=TV_MODUL_4B_ETHERNET> [DIAGSERVICE]

MCDDiagService<id=34617, job=com.bmw.psdz.jobs.uds.MCD3_PrepareECUforBLUpdate, service=CDTCS - ControlDTCSetting, description=error: negative response : serviceNotSupported, link=TV_MODUL_4B_ETHERNET> [DIAGSERVICE]

MCDDiagService<id=230634, job=com.bmw.psdz.jobs.uds.MCD3_PrepareECUforBLUpdate, service=DSC - DiagnosticSessionControl, description=error: negative response : conditionsNotCorrect, link=TV_MODUL_4B_ETHERNET> [DIAGSERVICE]

[TV_MODUL - 4B] prepareECUforBLUpdate finished [PROGRESS]

[TV_MODUL - 4B] authenticateECUforBLUpdate started [PROGRESS]

[TV_MODUL - 4B] authenticateECUforBLUpdate finished [PROGRESS]

[TV_MODUL - 4B - flsl_0000050c-005_000_027] Transaction type: blFlash; Message: TA started [TRANSACTION]

[TV_MODUL - 4B] performECUBLUpdate started with protocol UDS [PROGRESS]

[TV_MODUL - 4B - flsl_0000050c-005_000_027] Transaction type: blFlash; Message: 0% progress on ECUId:TV_MODUL_0x4B [0% of flsl_0000050c-005_000_027] [TRANSACTION]

MCDDiagService<id=276649, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUFlashBL, service=RDBI_RMA - ReadDataByIdentifier ReadMemoryAddress, description=error: negative response : requestOutOfRange, link=TV_MODUL_4B_ETHERNET> [DIAGSERVICE]

MCDDiagService<id=56634, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUFlashBL, service=RC_EM_IE - RoutineControl EraseMemory IndicatedErasing, description=error: negative response : conditionsNotCorrect, link=TV_MODUL_4B_ETHERNET> [DIAGSERVICE]

[TV_MODUL - 4B - flsl_0000050c-005_000_027] Transaction type: blFlash; Message: 0% progress on ECUId:TV_MODUL_0x4B [0% of flsl_0000050c-005_000_027] [TRANSACTION]

[] job failed with negative response error:

code: repeat job

description: Service RC_EM_IE returned a negative response with response code conditionsNotCorrect; LinkName: TV_MODUL_4B_ETHERNET

severity: ERROR

[THROWABLE]

[TV_MODUL - 4B - flsl_0000050c-005_000_027] Transaction type: blFlash; Message: TA finished [TRANSACTION]

[TV_MODUL - 4B] There was an error during TAL execution, please check the log files. [WARN]

[TV_MODUL - 4B] - [Exception - TV_MODUL - 4b] job failed with negative response error:

code: repeat job

description: Service RC_EM_IE returned a negative response with response code conditionsNotCorrect; LinkName: TV_MODUL_4B_ETHERNET

severity: ERROR

[TV_MODUL - 4B] installECUBL started [PROGRESS]

[TV_MODUL - 4B] installECUBL finished [PROGRESS]

[TV_MODUL - 4B] finalizeECUBLUpdate started [PROGRESS]

[TV_MODUL - 4B] finalizeECUBLUpdate finished [PROGRESS]

[] There was an error, please check the log files. [WARN]

[] - [Exception - TV_MODUL - 4b] job failed with negative response error:

code: repeat job

description: Service RC_EM_IE returned a negative response with response code conditionsNotCorrect; LinkName: TV_MODUL_4B_ETHERNET

severity: ERROR

[] finalizeVehicleFlash started [PROGRESS]

MCDDiagService<id=230900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeVehicleFlash, service=DSC - DiagnosticSessionControl, description=error: timeout, link=HU_CIC_63_ETHERNET> [DIAGSERVICE]

MCDDiagService<id=230900, job=com.bmw.psdz.jobs.common.MCD3_FinalizeVehicleFlash, service=DSC - DiagnosticSessionControl, description=error: timeout, link=HU_CIC_63_ETHERNET> [DIAGSERVICE]

[] 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 18s". [C206]

Read SVT after TAL execution started.

Read SVT after TAL execution finished.
Image
Image
Image

Image

Image

Image

Image

Image

Image
 
#2 ·
Two things. Never read VCM as this only reads the info saved inside the VCM not the ECUs currently installed.

Second, did you add HO WORD “TVT2”?


Sent from my iPhone using Tapatalk
 
#3 · (Edited)
Okay. When I read ecu instead og read vcm, there was an error in TAL calculation, and when i went to tal processing, the text next to slot of ecus was yellow and said something like "not executionable" or something like that.

No, do I need to add that? All the forums I read just coded the module.


I only have one HO word (k235), is that normal?

So i should add TVT2 in Ho Wort and VO code CIC and TV module?

But why won't it flash the module?

Buy then again, it it helps just adding the HW Worrz I don't need to flash the module it self, but only vo code it.


Sendt fra min SM-G991B med Tapatalk
 
#4 ·
Because esys doesn’t know that the car now has the new module. They are different. TVT2 is an upgrade to 601 therefore the HO WORD is the identifier to this. You can’t flash a module with the wrong files, esys knows what should be fitted. Add TVT2, calculate the TAL correctly and you should be able to flash it.
 
#6 ·
Up to you mate, depends what you are wanting to achieve. Either way, add TVT2 as HOWORD and write the FA to the VCM. Now you can flash and code correctly as your FA is now as it should be.


Sent from my iPhone using Tapatalk
 
#8 ·
Enet is absolutely fine mate. Coding the unit with the correct FA will mean it’s coded correctly. However, there is an issue with these ECUs where they don’t save the channels after scanning. The fix for that is to flash it. I’ve had mine fitted for 3 years and needed to flash it twice.


Sent from my iPhone using Tapatalk
 
#10 ·
Have you added the wiring from the TVT2 to the RSE unit?


Sent from my iPhone using Tapatalk
 
#15 ·
Why would the old module have not worked? Something seems wrong if you’re getting no signal. Check wiring is correct on the FBAS. You will need to force flash the module. This can be done by using TAL filter editor. You should also write the new FA to the VCM. Code an ECU with update VCM after tal….. ticked in esys options.


Sent from my iPhone using Tapatalk
 
#16 ·
The old module would work in a country wich broadcast dvb-t1 signal, but herefter in Denmark it is only dvb-t2, so therefore there is no signal.
The fbas cable from HU to TV is factory fitted. The only fbas cable i have run is from RSE to tv module.

So I need to flash the TV module to same i level as my car, even though it is already coded to the car ?

I have never tried force flashing ( i don't even know how that works :/)

Sendt fra min SM-G991B med Tapatalk
 
#19 ·
Yes


Sent from my iPhone using Tapatalk
 
#18 ·
Now I understand based on your location :)

Open TAL FILTER EDITOR and take a look at what information is needed. Basically you are going to load your SVT, edit the line for the TV MODULE to force BTLD/SWFL/CAFD

Save this and then load it on the tal calculation page and calculate the TAL again. This will now show the TV MODULE as requiring a flash.

Time to learn :)


Sent from my iPhone using Tapatalk
 
#21 ·
That is 100% correct. You need to find the line that corresponds to your TV module. You can tell this using its diagnostics address. For example the HU is 0x63 and DME IS 0x12. I forget what the TV MODUL is but you can see it on the TAL Calculation page next to the ECU.

Edit:
Looks like 4b.


Sent from my iPhone using Tapatalk
 
#23 ·
Choose BLFLASH, SWDEPLOY AND CDDEPLOY. They are SWFL and CAFD.


Sent from my iPhone using Tapatalk
 
#24 ·
Cool, thanks.

Ok, this is for the slow kid (me).
I Edit in talfilter to force flash the TV module.

Tal calculation- read fa - activate fa - load the edited svt ( or read ecu?) - complete flash - choose i step shipment - calculate - hw I'd from svtactual ? - calculate TAL- expert mode - load tal - load svt target - read fa (vcm) - check software- hope tv module appears and flash with fingers crossed [emoji1696]?

Sendt fra min SM-G991B med Tapatalk
 
#25 ·
So once you have calculated the SVT target/update (sol) that file never changes, it is what it is. Read FA, read ECU. Load the file you just made in the section for edited TAL on the tal calculation window. You will now see a new symbol next to TV module once loaded. Calculate TAL again on this page, save, press execute and you will now see TV MODULE in TAL processing.


Sent from my iPhone using Tapatalk
 
#27 ·
The SVT ACTUAL mate. The target is irrelevant for this process so leave it calculated and unchanged. You’ve already edited the file as you showed in the pictures. Try not to over complicate this. All you’re doing is taking the SVT actual, telling esys that a specific module MUST be included in the TAL based on the changes you made. It’s all simple logic.


Sent from my iPhone using Tapatalk
 
#28 ·
Haha, you are right.

But i often just press the buttons because I know that is how it works, but really I don't know what each step does/mean.

I will give a go again, and hopes the flashing doesn't fail. I hate it when it goes to transport mode with alle the errors. It takes forever do delete in ista with a slow enet cable.

Sendt fra min SM-G991B med Tapatalk
 
#29 ·
That’s the thing, most people just press this and that with no idea what the functions are actually doing.

Show me your TAL processing window before you start, or, if the flash has started you can monitor the progress for each part of the SVK by expanding the window up on TAL Processing.


Sent from my iPhone using Tapatalk
 
#31 ·
There is NO NEED to edit the SVT ACTUAL. Load the SVT ACTUAL in the tal filter editor. Make the changes and save. Now go to tal calculation page and load the file you just saved in the section below the SVT target. Now click calculate TAL, execute. It’s just logic mate. You are loading the edited TAL file into the tal calculation page to force the changes.


Sent from my iPhone using Tapatalk
 
#33 ·
Your tal processing is very wrong if you have HWINSTALL OR HWDEINSTALL in the TAL. Check you ilevel shipment date.


Sent from my iPhone using Tapatalk
 
#35 ·
Ok, then you need to workout why you have RED ECUs in the SVT tree. There should NOT be HWDEINSTALL/HWINSTALL in the TAL.


Sent from my iPhone using Tapatalk
 
#36 ·
Any ECUs with missing SWE should be deleted from the TAL to make life easier.


Sent from my iPhone using Tapatalk
 
#38 ·
I can do it remotely mate, won’t take me long. I was trying to empower you :)

Send me your AnyDesk details in PM


Sent from my iPhone using Tapatalk
 
  • Like
Reactions: Sixaxisbuild
#42 ·
Hi Davyg, ive been trying to force an flash over a japanese tv module using esys, ive edited ist, tryed force update, nothing works because the hwel found is different to expected as the car is FA uk now. Ive also tried editing the ist and changing the hwel info but this doesnt work either, any ideas or do you fancy teamviewering and having a go? i have latest pszdata etc, thanks.
 
#47 ·
Got it done on both cars in the end, strange one. The first car i did calculated the tal as normal using 3.30 after swt by ecu and then used ist, soll and tall files in 3.27 and to flash and it went through! Thought it would be easy for the second car, it wasnt. I ended up using the soll calc from the first car and combining it with the ist from the second car, calc the tal and used 3.40 to program the module. It failed at the last swf so had to manipulate the files again and reflash and then it went through. So, i think the version of esys didnt matter in my case. For some reason the calculated soll was giving an error in the expected sgib between the ist and the actual.
luckily for me both cars are f10 made within 3 months of aech other and the sw and hw of the tv module was the same.
advice is really spend a lot of time really trying to understand what the processes and buttons do and the you can manipulate the files, trim them so you are only dealing with relevant modules and keep going till it works.
changing the istep as some have advised did nothing to remedy the errors in my case (expected sgid not matching).
To be clear i have flashed a japanese tv module to receive uk TV channels and work in the uk, which is probably not normal.