[Studie]

For those who have a fresh installation of WINKFP and need to setup their configuration file for flashing. I have uploaded a screenshot of the settings I use when flashing with the ICOM and K+DCAN cable.

These settings will work for flashing any module on any E-chassis car. If you have any other errors, it would probably be because the daten/chassis data has not been installed/imported correctly.

Attached is the screenshot for reference.

[Enabled]

This is bad info.
You should use the settings that are best suited for the module you are trying to flash.



"Programming Voltage" is only used when you have to flash some DMEs that need +12V added to a certain pin to allow writing. Only the ICOM or OPPS head can give programming voltage, K+DCAN cannot.
When you check the box for "Programming Voltage" you are instructing WinKFP to make the ICOM or OPPS head give programming voltage. You will have error with K+DCAN.

"Force program programming in comfort mode" will flash the .0pa as well as the .0da. This isn't always necessary, when .0da is enough.

"Fast baudrate" can cause problems with some modules.

[Bimmer540]

What are the best settings in Winkfp?

[PhilipM]

I have fast baudrate off, "force program programming.." only on in special cases, for example if you suspect a problem in the original program flash, or you know the data flash and program flash are not compatible.

For example, an Engine ECU will have a program flash which is shared by a few versions, and a data flash which is specific to differences. You might see this as a 325d and a 330d have different program flashes on the same ECU. On just one of them, the 330d for example, you might see that they all share the same program flash, but different data flash for auto or manual, different emissions specs etc.

Usually data flash areas can be exchanged with other data flashes for the same program flash.

If you put the wrong data flash onto an ECU, this is where you will need the "force program area" tickbox.
WinKFP would check the data flash, assume it has the correct program flash, and only re-write the data area. If you tick the box, it will re-program the program area and data area together.
This usually takes longer, so you would only need this if you have an ecu with a damaged file, repaired it with the wrong file type to get it to communicate, and then use WinKFP to do everything from start to finish.


I also have UIF write in expert mode (you would very rarely need the expert mode)
If you switch off the UIF write boxes, the ECU will update, but it will not show the new software or part numbers.
The UIF is User Info Field, where the VIN, part numbers, programming date etc is written.
Some ECUs only have limited space for these, each programming adds a new UIF.

If you have an ECU which has filled 15 UIF slots, untick those boxes and it won't add any new ones and run out of space. If you are programming back to original (keeping the same software version) this will help you so you don't run out of slots.

[Bimmer540]

Does winkfp make a backup before programming? and where is this restored? And if it's necessary how to set back a backup?

[PhilipM]

WinKFP does not make any backups, but it will also only program certain areas.
It will not write over any areas holding the ISN or rolling codes for example.

One benefit of WinKFP is that you can choose a file to flash, instead of automatic determination.
Update ZUSB = This is automatic determination where it will select the latest file from the .HIS file in the ECU data folder
Choose ZUSB = You can select which ZUSB to flash

Ista/p will always do automatic determination, so if you are converting auto to manual for example, ISTA/P will update to a new automatic file.
If you know the manual file number, WinKFP will force the program to manual version.

It can not program to anything older that is no longer in the SP Daten, so older SP daten can be good to have.

A good idea to prepare for problems is if you are going to be changing a software type, first click the "update ZUSB", enter a VIN, click done, and then "prog ZB update"
This will show a box with your current ZUSB number and the new target it wants to program.
Take a note of these, as you might not find you original current ZUSB number to go back to, but at least you will know what to program it to if everything goes wrong. Do no continue at this point, cancel the programming.
Now you should at least know what a correct working software for the ECU will be, even if the changes go bad.

To change a ZUSB to something different, you will use the "choose ZUSB" button and manually select it. This would allow you to program a used 525d ECU to 530d for example ( "update zusb" would update it to a new 525D)

WinKFP is also good for ECU recovery.
If the ecu has been bricked during remapping for example, you might find that ISTA/P and diagnostics will not talk to it.
WinKFP can often still connect for basic identification, and allow the file to be programmed back to the ECU.

Finally, there is WinKFP expert mode.
If you imagine the WINKFP is pretty hardcore, the expert mode is even more so. Almost all of the safety features are switched off, and it allows you to do anything. This will mean you can make very big mistakes, but it is strong for resolving big problems too.

I use it when repairing FRM3 modules. You can load any FRM3 eeprom onto an FRM so it communicates again, but sometimes if you try to reprogram, WinKFP and ISTA will believe the software (from the eeprom) is the wrong version for the module. WinKFP expert mode can force the correct version.
Ideally if you can find and use the correct eeprom file for the FRM, you will not have this problem, but it can be hard to find the correct version.

I have seen some of the FRM3 EEPROM files are missing the BMW HW number, and WinKFP will refuse to program, and Expert mode will power through any errors or incompatibilities.

[atomantmk]

I use it when repairing FRM3 modules. You can load any FRM3 eeprom onto an FRM so it communicates again, but sometimes if you try to reprogram, WinKFP and ISTA will believe the software (from the eeprom) is the wrong version for the module. WinKFP expert mode can force the correct version.
Ideally if you can find and use the correct eeprom file for the FRM, you will not have this problem, but it can be hard to find the correct version.

I have seen some of the FRM3 EEPROM files are missing the BMW HW number, and WinKFP will refuse to program, and Expert mode will power through any errors or incompatibilities.

This part is interesting, how to flash FRM3 module?

[lupu_sandu]

Why you load any eep from FRM3 when you can extract original eep from D FLASH partition of MCU.

[PhilipM]

Why you load any eep from FRM3 when you can extract original eep from D FLASH partition of MCU.

My Xprog has never managed to read the D flash from a corrupted FRM.
If I do select it, it would read an output an empty file of 0kb.

I have looked at some collections of FRM repair files, and in some of those I have also seen P flash reads, EEp reads, and D flash read of 0kb

Maybe I will try UPA next time to see if that is any better.

If there are any special tips for reading the D flash, please let me know

[bmwadriatic]

I want to flash a costumers DDE because of bad remap tune. Someone can help with it? I have fresh installation of standard tools and never worked with winkfp. K+Dcan is working fine in ista-d.