I did read your previous post about this. As I succesfully was able to "read info" with version 1.4.2.2 and you weren't back then... I'm wondering why that is, is it a version issue...

that makes sense. bootmode should let you read any file off the ecu though. 

My software is faster than Galletto/KWP2000Plus and anything that supports boot mode. But my software only works if the tuner hasn't disabled the few different services in the ECU that allow me to use the KWP2000 protocol to read from the flash memory.

If you get a message about "ServiceNotSupported" while trying to read from the ECU, then that means the tuner has disabled the RequestUpload KWP2000 service. This prevents reading from the ECU using the standard documented KWP2000 protocol. The only way to read the ECU flalsh at this point is to use boot mode, or to do some fancy code injection ECU hacking which I am working on. Don't hold your breath waiting for me to implement this feature though, because it is a the end of a long list of things I need to do.

Try using the S4 memory layout to do a read. That should let you know if it is the correct size and location for the flash memory chip. There is no way that I know of currently to determine if the flash chip is a BB or BT though.

Thanks for the log file, this message seems to identify the problem:

"Received negative response for service ID: StartDiagnosticSession, with response code: ConditionsNotCorrectOrRequestSequenceError"

This only appears to be occurring when trying to start a programming session, because you have no problems starting a standard session to read the ECU info.

My only thought at this point, is perhaps it will work in the car, but not on the bench, or there is something I am missing that the ECU requires before entering programming mode.

The log file you posted, shows that the problem it is having will prevent you from reading and writing. So I don't believe there is any reason to test writing at this point. But perhaps reading from inside the car may work.

@ arne_rs4 :

Please be so kind, to add the logfile of the nefmoto flasher. This will perhaps tell why you get the 'incorrect coded' error.

Press in the grey area, above File to Flash :  the Log File button. Then choose Open Log File. Save this file to disc please,
and post over here in the forum.

Thanks,

Pascal

@ Arne :

Thanks for the log. This will perhaps help Tony to work out this problem.

I have a question relating to your and your friend's ecu. Are these exactly the same ecu's ? :

8D0907551K 0001 - 0261207001 - 1037360387 RS4 - 0xCFCD

(thats the one i found on internet, and added the checksum to it)

On your car's ecu, the readout was the original file which was in it, and you'd wrote that back, and
suddenly it throws the coding-error in vagcom ?

I get the feeling that the little config-eeprom-chip inside the ecu got a bit mangled up when writing to the
ecu itselfe.. therefore the coding must be restored to remove this error. We need to investigate this.

Do you by chance also own interfaces like vagdashcom/ecutool or vag k+can commander ? then a readout is
possbile, and a compare against the original chip-content and the new content after writing.

Other forum-members did some writes to their ecu also, and perhaps they also have this error? Ifso, please
do post.

Thanks,

Pascal