VTS_Tibi
12th February, 2013, 06:27 PM
Hi Guys,
I read out the original dump from an AM29F400BB from a Siemens Simos 3PG ECU (Skoda Fabia 1.2 12V with Siemens 5WP44223) with Willem GW-4X and an adapter. Original file attached.
I would have to write back the other dump which is attached, but when I simply write it back onto the ECU the car does not start, immo light blinking and gives the following error numbers:
-16990 PCM memory fault
-17978 Engine control unit blocked
-16985 Internal Control Module checksum Error
So it throws a checksum fault BUT the checksum was corrected on the new dump!
----------------------------------------------------------------------------------------
On an other site I read the following:
It's a siemens ecu. It means, when you're done, you have to decode it to siemens protocol.
A thread here in DK:
So, the problem with write/erase fails is that the data lines are crossed (for routing simplification): when the C167 "wants" to write the "sequences" (see the AMD datasheet), the memory doesen't see the right values.
Actually, this problem is well known in Siemens automotive ECU units.
For example, in some cases you must write "44h" on the proc side, if you want the memory to see part of the unlock sequence "A0h".
So, I have to rewrite (and recompile) the minimon driver in order to correct the memory patterns.
Progs as WinOls and ECM2001 have integated option to code/decode dumps BIN<->SIE, due to swapped data lines.
For comparision, find two attached files: one is in-circuit read with Minimon, the other is read by eeprom programmer (flash chip desoldered).
link: http://www.digital-kaos.co.uk/forums/f175/vag-simos2-ecu-read-galetto-186967/#post1685058
Could it happen that the new dump simply needs decoding, and this is the reason for the non starting?! Remember, dump was read out with the flash desoldered, not ECU in boot mode!!!!
I read out the original dump from an AM29F400BB from a Siemens Simos 3PG ECU (Skoda Fabia 1.2 12V with Siemens 5WP44223) with Willem GW-4X and an adapter. Original file attached.
I would have to write back the other dump which is attached, but when I simply write it back onto the ECU the car does not start, immo light blinking and gives the following error numbers:
-16990 PCM memory fault
-17978 Engine control unit blocked
-16985 Internal Control Module checksum Error
So it throws a checksum fault BUT the checksum was corrected on the new dump!
----------------------------------------------------------------------------------------
On an other site I read the following:
It's a siemens ecu. It means, when you're done, you have to decode it to siemens protocol.
A thread here in DK:
So, the problem with write/erase fails is that the data lines are crossed (for routing simplification): when the C167 "wants" to write the "sequences" (see the AMD datasheet), the memory doesen't see the right values.
Actually, this problem is well known in Siemens automotive ECU units.
For example, in some cases you must write "44h" on the proc side, if you want the memory to see part of the unlock sequence "A0h".
So, I have to rewrite (and recompile) the minimon driver in order to correct the memory patterns.
Progs as WinOls and ECM2001 have integated option to code/decode dumps BIN<->SIE, due to swapped data lines.
For comparision, find two attached files: one is in-circuit read with Minimon, the other is read by eeprom programmer (flash chip desoldered).
link: http://www.digital-kaos.co.uk/forums/f175/vag-simos2-ecu-read-galetto-186967/#post1685058
Could it happen that the new dump simply needs decoding, and this is the reason for the non starting?! Remember, dump was read out with the flash desoldered, not ECU in boot mode!!!!