|
Title: Flash checksum does not match - what does this Log message mean? Post by: Higgy on April 09, 2011, 02:38:19 PM Hi all,
I have just flashed my VAG 1.8T ME7.5 06A906032SJ back with the orig factory map. Before saying a big THANK YOU ;D I want to check the following. While it was flashing I noticed this appearing: LOG: Checksum is incorrect. USER: Flash checksum does not match, reading flash data is necessary. USER: Requesting upload from ECU for address range 0x00820000 to 0x0082FFFF. LOG: Sent message with service ID RequestUpload LOG: Received message with service ID RequestUploadPositiveResponse USER: Request upload from ECU succeeded. USER: Starting data transfer. There are at least 3 of them over the 16 sectors which are written. I have been for a 20min drive and everything ran fine, well apart from being -30BHP as it is on factory map! I have turned ignition on-off about 10 times and have started the engine now 3 times since further scanning with VAG-COM and NefMoto. I noticed going back through old logs, that this message also comes up when I READ the old flash containing the map I just overwritten. So is this a common message, or something to do with ME7.5? I don't want the nasty Checksum situation where my engine won't start sometime. I have attached a cut/paste log, that only includes the WRITING map part. Many Thanks. Title: Re: Flash checksum does not match - what does this Log message mean? Post by: julex on April 10, 2011, 09:34:32 AM Hi all, I have just flashed my VAG 1.8T ME7.5 06A906032SJ back with the orig factory map. Before saying a big THANK YOU ;D I want to check the following. While it was flashing I noticed this appearing: LOG: Checksum is incorrect. USER: Flash checksum does not match, reading flash data is necessary. USER: Requesting upload from ECU for address range 0x00820000 to 0x0082FFFF. LOG: Sent message with service ID RequestUpload LOG: Received message with service ID RequestUploadPositiveResponse USER: Request upload from ECU succeeded. USER: Starting data transfer. There are at least 3 of them over the 16 sectors which are written. I have been for a 20min drive and everything ran fine, well apart from being -30BHP as it is on factory map! I have turned ignition on-off about 10 times and have started the engine now 3 times since further scanning with VAG-COM and NefMoto. I noticed going back through old logs, that this message also comes up when I READ the old flash containing the map I just overwritten. So is this a common message, or something to do with ME7.5? I don't want the nasty Checksum situation where my engine won't start sometime. I have attached a cut/paste log, that only includes the WRITING map part. Many Thanks. I am pretty sure it works this way. To avoid unnecessary flashing of blocks that haven't changed the flasher program first reads off cheksums form ECU for a given block and compares them to the ones in file you're trying to flash. If they match, it skips over to next block. If they don't, it flashes the new block into ECU... It is normal and no cause for concern. Title: Re: Flash checksum does not match - what does this Log message mean? Post by: Tony@NefMoto on April 11, 2011, 10:25:39 AM Everything is working normally when you get the "Checksum is incorrect" messages. If anything fails, you will get notification windows popping you up telling you what went wrong.
When reading and writing to flash memory, the checksum of the current sector is checked to determine if it is necessary to read or write that sector. If the checksums match, then the sector can be skipped because we know there are no changes to the data in that sector. The current version of the NefMoto ECU Flasher 1.7.0.0 does not support skipping sectors. It will tell you the sector can be skipped, but then it reads or writes it anyway. Version 1.7.1.0 which should be out in a few days will support feature licenses for "fast read" and "fast write" that will skip sectors that have no changes. Title: Re: Flash checksum does not match - what does this Log message mean? Post by: judeisnotobscure on April 11, 2011, 01:35:56 PM sweet... i can't wait for faster flashing.
Title: Re: Flash checksum does not match - what does this Log message mean? Post by: julex on April 12, 2011, 06:57:03 AM Everything is working normally when you get the "Checksum is incorrect" messages. If anything fails, you will get notification windows popping you up telling you what went wrong. When reading and writing to flash memory, the checksum of the current sector is checked to determine if it is necessary to read or write that sector. If the checksums match, then the sector can be skipped because we know there are no changes to the data in that sector. The current version of the NefMoto ECU Flasher 1.7.0.0 does not support skipping sectors. It will tell you the sector can be skipped, but then it reads or writes it anyway. Version 1.7.1.0 which should be out in a few days will support feature licenses for "fast read" and "fast write" that will skip sectors that have no changes. Please make sure there is always an option to force flash whole file even if the algorithm thinks the checksums are the same. Title: Re: Flash checksum does not match - what does this Log message mean? Post by: Tony@NefMoto on April 12, 2011, 01:06:15 PM There are separate buttons for read and fast read, and write and fast write.
|