[azwgh]

Hi All,

I'm trying to program CHAMP2 module but I'm getting the error:

Code:

[HU_CHAMP2 - 63] - [Exception - HU_CHAMP2 - 63] job failed with negative response error:
code: the programming dependencies are not correct
description: FinalizeECUFlash failed - service RoutineControl CheckProgrammingDependencies delivered incorrectResult; LinkName: HU_CHAMP2_63_ETHERNET_63
severity: ERROR

I wanted to update the version CHAMP2 in my bench setup. Originally it was:

Code:

btld_000014e0_002_007_000
cafd_000000f9_007_003_114
flsl_0000152B_002_007_000
hwel_00001770_024_000_000
ibad_000014e3_003_019_003
NAVD_0000085f_255_000_197
swfl_00000a24_002_007_000
swfl_00000a26_002_007_000
swfl_00000a31_002_007_000
swfl_000014e4_002_007_001
swfl_000014e5_002_007_000
swfl_0000152c_002_007_000

This CHAMP2 is from F20, but I had no FA from this car, so I used FA from F10. During the TAL calculations HWEL didn't match exactly, but I simply ignored it. I selected a shipment version that contained a HWEL close to the one I have on my desk. However, it used two or three more swfl's swfl_00000a2a, swfl_00000a2f and possibly swfl_00000a25. I manually changed TAL file to avoid complains of wrong HWEL.
When I started the flashing flsl, btld and some swfl were transferred correctly, however swfl_00000a2a failed several times at 3% with the mentioned error:

Code:

[HU_CHAMP2 - 63] - [Exception - HU_CHAMP2 - 63] job failed with negative response error:
code: the programming dependencies are not correct
description: FinalizeECUFlash failed - service RoutineControl CheckProgrammingDependencies delivered incorrectResult; LinkName: HU_CHAMP2_63_ETHERNET_63
severity: ERROR

After that I got three entries:
UNKN_00000000_000_000_000

Then I wrote FA myself based on the bimmer.work's equipment and I got correct HWEL in calculations. Calculations didn't want to flash the extra swfl_00000a2a, swfl_00000a2f and swfl_00000a25.
I tried to flash one by one without any success.
When I tried to flash an extra swfl_00000a2f it got to the list, one entry UNKN_00000000_000_000_000 disappeared, but others UNKN were still there. So I end up with:

Code:

btld_000014e0_003_010_000
flsl_0000152B_003_010_000
hwel_00001770_024_000_000
ibad_000014e3_003_019_010
NAVD_0000085f_255_000_197
swfl_00000a24_003_010_000
swfl_00000a26_003_010_000
swfl_00000a2F_003_010_000    <----- new one, shouldn't be there
swfl_00000a31_003_010_000
swfl_000014e4_003_010_000
swfl_000014e5_003_010_000
swfl_0000152c_003_010_000
UNKN_00000000_000_000_000    <----- new one, shouldn't be there

I tried to flash again several times, with one entry at the time, with new/old versions but nothing helped.
I tried to flash it with files with an invalid content, and some of them were replaced by: UNKN_00000000_000_000_000.

I'm aware that this is my fault, but I would like to know how is it possible to fix it.
Another question could be if there is an method to remove swfl's from that list?
At this moment I can see CHAMP2 in esys, but no in ISTA. The display connected to CAHMP2 shows "no signal". The internal fan is on. I believe it stuck in bootloader.

[jaramillo]

Hello,

Just start with a F20 FA 2012-2013, with 663+6NH, check if you champ has nav and add more options to FA based on the HW.
A second option is to share HWEL or pn, Maybe Node can help you with part implementation in terms of I level and equipment.
And of course forcing a flash with diff in HWEL could end with a bricked unit if you dont know what are you really doing

[Node]

SWFL A2A is NEVER used for 1770_24 HWEL which does not have corresponding hardware for it hence your problem.

---

I can look it up later.

---

P.S. SAME with A2F.

[Node]

So you can flash this unit with both F10 and F20 target as it was used on both.

For F20 you could use FA with 1H71 type code and following options: 606, one or both of 6AE/6NS, none of 3AG/654, from 12-07-500 to 13-03-505.

For F10 - 5A11 and: 606, one or both of 6AE/6NS, none of 3AG/5DL/601/609/654/6UK, same factory iLevels.

In the end the list of things should look like (for both F10/F20 and iLevel 13-03-500):
BTLD 000014E0_002_011_001
CAFD 000000F9_007_006_006
FLSL 0000152B_002_011_000
HWEL 00001770_024_000_000
SWFL 00000A24_002_011_001
SWFL 00000A26_002_011_000
SWFL 00000A31_002_011_000
SWFL 000014E4_002_011_001
SWFL 000014E5_002_011_000
SWFL 0000152C_002_011_000

P.S. I'm still stumped again, but I should probably not be surprised anymore that people totally disregard HWEL mismatch and flash anyway... Then cry that unit is bricked, which luckily did not happen in this case, because at least bootloader and flashloader just happened to be correct by chance.

[azwgh]

Thanks for your responses. I messed one thing. In the first post I wrote that the unit is from F20, but unit is from F30, I used F020 in esys co connect to it.

Before I started the thread I already had FA from F30 with typeKey="3E12" and the equipment: 1CA, 230, 240, 249, 2AT, 2PA, 302, 423, 428, 431, 4CG, 507, 520, 521, 534, 544, 575, 5DA, 606, 612, 615, 616, 698, 6AA, 6AB, 6NL, 812, 850, 853, 880, 8KA, 8S2, 8S3, 8SM, 8TG, 8V1
When I did the calculations with this FA I got the correct TAL, with correct HWEL 1770_24 (no change), and correct SWFL to be programmed. But when I programmed using this TAL I'm still getting the error "code: the programming dependencies are not correct" and SWFL_00000A2F_003_010_000 and UNKN_00000000_000_000_000 are still there.

In the end the list of things should look like (for both F10/F20 and iLevel 13-03-500):
BTLD 000014E0_002_011_001
CAFD 000000F9_007_006_006
FLSL 0000152B_002_011_000
HWEL 00001770_024_000_000
SWFL 00000A24_002_011_001
SWFL 00000A26_002_011_000
SWFL 00000A31_002_011_000
SWFL 000014E4_002_011_001
SWFL 000014E5_002_011_000
SWFL 0000152C_002_011_000

I fully agree with this list, the problem is that I don't know how to make SWFL_00000A2F_003_010_000 and UNKN_00000000_000_000_000 to disappear from the read ECU list. Writing SVT to ZGW without these positions in CHAMP2 does not help.
Is there a way to remove all SWFL entries and start from scratch? eg. using tool32? Or use a serial console to connect to CHAMP2?

P.S. I'm still stumped again, but I should probably not be surprised anymore that people totally disregard HWEL mismatch and flash anyway... Then cry that unit is bricked, which luckily did not happen in this case, because at least bootloader and flashloader just happened to be correct by chance.

I think that bootloader and flashloader think that they're on a different HWEL and they expect more SWFL to come.

[Node]

I do not understand your problem. Give ESys CORRECT SVT ist (as the unit has NOW with all wrong things) and correct SVT soll and it will make proper TAL, which will fix these wrong SWFLs.

[azwgh]

I do not understand your problem. Give ESys CORRECT SVT ist (as the unit has NOW with all wrong things) and correct SVT soll and it will make proper TAL, which will fix these wrong SWFLs.

flashing with the proper TAL still gives me the same error.
TAL has information what to flash, but does not have information to remove particular SWFL.

[azwgh]

I attached the log from e-sys, FA, SVT and TAL

[Node]

CARE to EXPLAIN what the f*** are you doing??? IMHO SWFL A24_3_10_0 is NOT COMPATIBLE with your HWEL!!! Send SVT ist AT LEAST.

[azwgh]

CARE to EXPLAIN what the f*** are you doing??? IMHO SWFL A24_3_10_0 is NOT COMPATIBLE with your HWEL!!! Send SVT ist AT LEAST.

SWFL A24_3_10_0 is compatible with my HWEL according to calculations between Istep F020-12-07-533 (shipment) and F020-23-07-530 (target). I'm getting the same error when flashing with A24_2_7_0.
SWFL A2F_20_30_0 is not compatible with my HWEL, because it is A2F and because it is 20_30_0.
Still the question is whether it is possible to remove all SWFLs?

svt_actual attached