|
Title: Can´t erase flash memory Post by: Alcazer on November 30, 2013, 08:21:29 AM Hello,
Have a S4 with G-box and cant write any new map on it. It cant erase old map on it. Tried lowering baud rate but no change. I can successfully read but cant erase. So what can I do ? Please help and thank you for your time! 30/Nov/2013 03:19:13.335: USER: Writing ECU flash memory. 30/Nov/2013 03:19:13.353: USER: Negotiating communication timings. 30/Nov/2013 03:19:13.371: LOG: Reading current communication timings. 30/Nov/2013 03:19:13.375: LOG: Sent message with service ID AccessTimingParameters 30/Nov/2013 03:19:13.408: LOG: Received message with service ID AccessTimingParametersPositiveResponse 30/Nov/2013 03:19:13.409: LOG: Setting communication timing to defaults. 30/Nov/2013 03:19:13.414: LOG: Sent message with service ID AccessTimingParameters 30/Nov/2013 03:19:13.444: LOG: Received message with service ID AccessTimingParametersPositiveResponse 30/Nov/2013 03:19:13.445: LOG: Reading current communication timings. 30/Nov/2013 03:19:13.449: LOG: Sent message with service ID AccessTimingParameters 30/Nov/2013 03:19:13.498: LOG: Received message with service ID AccessTimingParametersPositiveResponse 30/Nov/2013 03:19:13.499: USER: Successfully changed to new communication timings. 30/Nov/2013 03:19:13.499: USER: Requesting security access. 30/Nov/2013 03:19:13.504: LOG: Sent message with service ID SecurityAccess 30/Nov/2013 03:19:13.548: LOG: Received message with service ID SecurityAccessPositiveResponse 30/Nov/2013 03:19:13.548: USER: Security access granted. 30/Nov/2013 03:19:13.549: USER: Negotiating communication timings. 30/Nov/2013 03:19:13.549: LOG: Reading current communication timings. 30/Nov/2013 03:19:13.552: LOG: Sent message with service ID AccessTimingParameters 30/Nov/2013 03:19:13.608: LOG: Received message with service ID AccessTimingParametersPositiveResponse 30/Nov/2013 03:19:13.608: LOG: Set timing parameters to new values. 30/Nov/2013 03:19:13.608: LOG: Reading communication timing limits. 30/Nov/2013 03:19:13.675: LOG: Sent message with service ID AccessTimingParameters 30/Nov/2013 03:19:13.720: LOG: Received message with service ID AccessTimingParametersPositiveResponse 30/Nov/2013 03:19:13.720: LOG: Requesting communication at timing limits. 30/Nov/2013 03:19:13.724: LOG: Sent message with service ID AccessTimingParameters 30/Nov/2013 03:19:13.774: LOG: Received message with service ID AccessTimingParametersPositiveResponse 30/Nov/2013 03:19:13.774: USER: Successfully changed to new communication timings. 30/Nov/2013 03:19:13.774: USER: Requesting security access. 30/Nov/2013 03:19:13.779: LOG: Sent message with service ID SecurityAccess 30/Nov/2013 03:19:13.808: LOG: Received message with service ID SecurityAccessPositiveResponse 30/Nov/2013 03:19:13.808: USER: Security access granted. 30/Nov/2013 03:19:13.808: USER: Validating flash memory starts at 0x00800000 and ends at 0x00900000. 30/Nov/2013 03:19:13.813: LOG: Sent message with service ID RequestUpload 30/Nov/2013 03:19:13.845: LOG: Received message with service ID RequestUploadPositiveResponse 30/Nov/2013 03:19:13.846: LOG: Flash start and end addresses are valid. 30/Nov/2013 03:19:13.850: LOG: Sent message with service ID RequestUpload 30/Nov/2013 03:19:13.875: LOG: Received message with service ID NegativeResponse 30/Nov/2013 03:19:13.876: LOG: Received negative response for service ID: RequestUpload, with response code: CanNotUploadFromSpecifiedAddress 30/Nov/2013 03:19:13.876: LOG: Flash start address is the lowest address. 30/Nov/2013 03:19:13.880: LOG: Sent message with service ID RequestUpload 30/Nov/2013 03:19:13.905: LOG: Received message with service ID NegativeResponse 30/Nov/2013 03:19:13.906: LOG: Received negative response for service ID: RequestUpload, with response code: CanNotUploadNumberOfBytesRequested 30/Nov/2013 03:19:13.906: LOG: Flash end address is the highest address. 30/Nov/2013 03:19:13.906: LOG: Flash memory addresses are valid. 30/Nov/2013 03:19:13.906: USER: Memory layout is valid. 30/Nov/2013 03:19:13.906: USER: Starting to flash data block. 30/Nov/2013 03:19:13.906: USER: Calculating flash checksum to determine if flashing is necessary for range: 0x00800000 to 0x00804000 30/Nov/2013 03:19:13.907: LOG: Validating flashed data checksum for address range 0x00800000 to 0x00803FFF. 30/Nov/2013 03:19:13.918: LOG: Sent message with service ID StartRoutineByLocalIdentifier 30/Nov/2013 03:19:13.955: LOG: Received message with service ID StartRoutineByLocalIdentifierPositiveResponse 30/Nov/2013 03:19:13.960: LOG: Sent message with service ID RequestRoutineResultsByLocalIdentifier 30/Nov/2013 03:19:13.985: LOG: Received message with service ID RequestRoutineResultsByLocalIdentifierPositiveResponse 30/Nov/2013 03:19:13.985: LOG: Checksum is correct. 30/Nov/2013 03:19:13.986: USER: Flash checksum matches new data, flashing is unnecessary, but flashing anyway. 30/Nov/2013 03:19:13.986: USER: Requesting flash memory erase for address range 0x00800000 to 0x00803FFF. Title: Re: Can´t erase flash memory Post by: Alcazer on November 30, 2013, 08:22:02 AM 30/Nov/2013 03:19:13.997: LOG: Sent message with service ID StartRoutineByLocalIdentifier
30/Nov/2013 03:19:14.031: LOG: Received message with service ID NegativeResponse 30/Nov/2013 03:19:14.031: LOG: Received negative response for service ID: StartRoutineByLocalIdentifier, with response code: RoutineNotCompleteOrServiceInProgress 30/Nov/2013 03:19:14.032: USER: ECU reports routine not complete while attempting to erase flash memory. 30/Nov/2013 03:19:16.502: LOG: Sent message with service ID TesterPresent 30/Nov/2013 03:19:16.520: LOG: Received message with service ID TesterPresentPositiveReponse 30/Nov/2013 03:19:19.006: LOG: Sent message with service ID TesterPresent 30/Nov/2013 03:19:19.027: LOG: Received message with service ID TesterPresentPositiveReponse 30/Nov/2013 03:19:21.512: LOG: Sent message with service ID TesterPresent 30/Nov/2013 03:19:21.534: LOG: Received message with service ID TesterPresentPositiveReponse 30/Nov/2013 03:19:23.743: LOG: User Prompt - Title: Sector Erase Failed Message: Failed to erase the memory sector. Press OK to skip this sector and continue, or Cancel to abort the flashing process. Result: OK 30/Nov/2013 03:19:23.743: USER: 2% complete. 30/Nov/2013 03:19:23.743: USER: Starting to flash data block. 30/Nov/2013 03:19:23.743: USER: Calculating flash checksum to determine if flashing is necessary for range: 0x00804000 to 0x00806000 30/Nov/2013 03:19:23.744: LOG: Validating flashed data checksum for address range 0x00804000 to 0x00805FFF. 30/Nov/2013 03:19:23.761: LOG: Sent message with service ID StartRoutineByLocalIdentifier 30/Nov/2013 03:19:23.790: LOG: Received message with service ID StartRoutineByLocalIdentifierPositiveResponse 30/Nov/2013 03:19:23.794: LOG: Sent message with service ID RequestRoutineResultsByLocalIdentifier 30/Nov/2013 03:19:23.822: LOG: Received message with service ID RequestRoutineResultsByLocalIdentifierPositiveResponse 30/Nov/2013 03:19:23.822: LOG: Checksum is correct. 30/Nov/2013 03:19:23.823: USER: Flash checksum matches new data, flashing is unnecessary, but flashing anyway. 30/Nov/2013 03:19:23.823: USER: Requesting flash memory erase for address range 0x00804000 to 0x00805FFF. 30/Nov/2013 03:19:23.835: LOG: Sent message with service ID StartRoutineByLocalIdentifier 30/Nov/2013 03:19:23.866: LOG: Received message with service ID NegativeResponse 30/Nov/2013 03:19:23.866: LOG: Received negative response for service ID: StartRoutineByLocalIdentifier, with response code: RoutineNotCompleteOrServiceInProgress 30/Nov/2013 03:19:23.866: USER: ECU reports routine not complete while attempting to erase flash memory. 30/Nov/2013 03:19:25.086: LOG: User Prompt - Title: Sector Erase Failed Message: Failed to erase the memory sector. Press OK to skip this sector and continue, or Cancel to abort the flashing process. Result: OK 30/Nov/2013 03:19:25.087: USER: 2% complete. 30/Nov/2013 03:19:25.087: USER: Calculating checksum for first sector flashed to determine which erase mode the ECU is using. 30/Nov/2013 03:19:25.087: LOG: Validating flashed data checksum for address range 0x00800000 to 0x00803FFF. 30/Nov/2013 03:19:25.099: LOG: Sent message with service ID StartRoutineByLocalIdentifier 30/Nov/2013 03:19:25.133: LOG: Received message with service ID StartRoutineByLocalIdentifierPositiveResponse 30/Nov/2013 03:19:25.137: LOG: Sent message with service ID RequestRoutineResultsByLocalIdentifier 30/Nov/2013 03:19:25.165: LOG: Received message with service ID RequestRoutineResultsByLocalIdentifierPositiveResponse 30/Nov/2013 03:19:25.165: LOG: Checksum is correct. 30/Nov/2013 03:19:25.166: USER: ECU appears to be in erase entire flash mode, restarting the flash process. 30/Nov/2013 03:19:25.166: USER: Starting to flash data block. 30/Nov/2013 03:19:25.166: USER: Requesting flash memory erase of entire flash memory. 30/Nov/2013 03:19:25.169: LOG: Sent message with service ID StartRoutineByLocalIdentifier 30/Nov/2013 03:19:25.199: LOG: Received message with service ID NegativeResponse 30/Nov/2013 03:19:25.199: LOG: Received negative response for service ID: StartRoutineByLocalIdentifier, with response code: RoutineNotCompleteOrServiceInProgress 30/Nov/2013 03:19:25.200: USER: ECU reports routine not complete while attempting to erase flash memory. 30/Nov/2013 03:19:25.200: USER: Writing ECU flash memory failed. 30/Nov/2013 03:19:25.200: USER: 100% complete. 30/Nov/2013 03:19:27.675: LOG: Sent message with service ID TesterPresent 30/Nov/2013 03:19:27.698: LOG: Received message with service ID TesterPresentPositiveReponse 30/Nov/2013 03:19:29.172: USER: Restoring Windows sleep mode. 30/Nov/2013 03:19:30.179: LOG: Sent message with service ID TesterPresent 30/Nov/2013 03:19:30.205: LOG: Received message with service ID TesterPresentPositiveReponse 30/Nov/2013 03:19:32.683: LOG: Sent message with service ID TesterPresent 30/Nov/2013 03:19:32.703: LOG: Received message with service ID TesterPresentPositiveReponse 30/Nov/2013 03:19:35.186: LOG: Sent message with service ID TesterPresent 30/Nov/2013 03:19:35.207: LOG: Received message with service ID TesterPresentPositiveReponse 30/Nov/2013 03:19:37.691: LOG: Sent message with service ID TesterPresent 30/Nov/2013 03:19:37.714: LOG: Received message with service ID TesterPresentPositiveReponse 30/Nov/2013 03:19:40.198: LOG: Sent message with service ID TesterPresent 30/Nov/2013 03:19:40.221: LOG: Received message with service ID TesterPresentPositiveReponse 30/Nov/2013 03:19:42.703: LOG: Sent message with service ID TesterPresent 30/Nov/2013 03:19:42.727: LOG: Received message with service ID TesterPresentPositiveReponse 30/Nov/2013 03:19:42.954: USER: Fast writing premium feature NOT enabled. 30/Nov/2013 03:19:43.024: USER: Truncated log file because it was larger than 10 megabytes. 30/Nov/2013 03:19:43.043: LOG: Log file truncation took: 00:00:00.0778492 30/Nov/2013 03:19:43.043: USER: Disabling Windows sleep mode. 30/Nov/2013 03:19:43.061: USER: Writing ECU flash memory. 30/Nov/2013 03:19:43.080: USER: Negotiating communication timings. 30/Nov/2013 03:19:43.097: LOG: Reading current communication timings. 30/Nov/2013 03:19:43.101: LOG: Sent message with service ID AccessTimingParameters 30/Nov/2013 03:19:43.133: LOG: Received message with service ID AccessTimingParametersPositiveResponse 30/Nov/2013 03:19:43.134: LOG: Setting communication timing to defaults. 30/Nov/2013 03:19:43.138: LOG: Sent message with service ID AccessTimingParameters Title: Re: Can´t erase flash memory Post by: Alcazer on November 30, 2013, 08:23:03 AM 30/Nov/2013 03:19:43.169: LOG: Received message with service ID AccessTimingParametersPositiveResponse
30/Nov/2013 03:19:43.169: LOG: Reading current communication timings. 30/Nov/2013 03:19:43.173: LOG: Sent message with service ID AccessTimingParameters 30/Nov/2013 03:19:43.223: LOG: Received message with service ID AccessTimingParametersPositiveResponse 30/Nov/2013 03:19:43.223: USER: Successfully changed to new communication timings. 30/Nov/2013 03:19:43.223: USER: Requesting security access. 30/Nov/2013 03:19:43.227: LOG: Sent message with service ID SecurityAccess 30/Nov/2013 03:19:43.273: LOG: Received message with service ID SecurityAccessPositiveResponse 30/Nov/2013 03:19:43.273: USER: Security access granted. 30/Nov/2013 03:19:43.273: USER: Negotiating communication timings. 30/Nov/2013 03:19:43.274: LOG: Reading current communication timings. 30/Nov/2013 03:19:43.277: LOG: Sent message with service ID AccessTimingParameters 30/Nov/2013 03:19:43.335: LOG: Received message with service ID AccessTimingParametersPositiveResponse 30/Nov/2013 03:19:43.335: LOG: Set timing parameters to new values. 30/Nov/2013 03:19:43.335: LOG: Reading communication timing limits. 30/Nov/2013 03:19:43.402: LOG: Sent message with service ID AccessTimingParameters 30/Nov/2013 03:19:43.444: LOG: Received message with service ID AccessTimingParametersPositiveResponse 30/Nov/2013 03:19:43.445: LOG: Requesting communication at timing limits. 30/Nov/2013 03:19:43.450: LOG: Sent message with service ID AccessTimingParameters 30/Nov/2013 03:19:43.517: LOG: Received message with service ID AccessTimingParametersPositiveResponse 30/Nov/2013 03:19:43.517: USER: Successfully changed to new communication timings. 30/Nov/2013 03:19:43.517: USER: Requesting security access. 30/Nov/2013 03:19:43.531: LOG: Sent message with service ID SecurityAccess 30/Nov/2013 03:19:43.554: LOG: Received message with service ID SecurityAccessPositiveResponse 30/Nov/2013 03:19:43.555: USER: Security access granted. 30/Nov/2013 03:19:43.555: USER: Validating flash memory starts at 0x00800000 and ends at 0x00900000. 30/Nov/2013 03:19:43.559: LOG: Sent message with service ID RequestUpload 30/Nov/2013 03:19:43.590: LOG: Received message with service ID RequestUploadPositiveResponse 30/Nov/2013 03:19:43.591: LOG: Flash start and end addresses are valid. 30/Nov/2013 03:19:43.595: LOG: Sent message with service ID RequestUpload 30/Nov/2013 03:19:43.620: LOG: Received message with service ID NegativeResponse 30/Nov/2013 03:19:43.620: LOG: Received negative response for service ID: RequestUpload, with response code: CanNotUploadFromSpecifiedAddress 30/Nov/2013 03:19:43.621: LOG: Flash start address is the lowest address. 30/Nov/2013 03:19:43.625: LOG: Sent message with service ID RequestUpload 30/Nov/2013 03:19:43.650: LOG: Received message with service ID NegativeResponse 30/Nov/2013 03:19:43.650: LOG: Received negative response for service ID: RequestUpload, with response code: CanNotUploadNumberOfBytesRequested 30/Nov/2013 03:19:43.650: LOG: Flash end address is the highest address. 30/Nov/2013 03:19:43.651: LOG: Flash memory addresses are valid. 30/Nov/2013 03:19:43.651: USER: Memory layout is valid. 30/Nov/2013 03:19:43.651: USER: Starting to flash data block. 30/Nov/2013 03:19:43.651: USER: Calculating flash checksum to determine if flashing is necessary for range: 0x00800000 to 0x00804000 30/Nov/2013 03:19:43.651: LOG: Validating flashed data checksum for address range 0x00800000 to 0x00803FFF. 30/Nov/2013 03:19:43.654: LOG: Sent message with service ID StartRoutineByLocalIdentifier 30/Nov/2013 03:19:43.690: LOG: Received message with service ID StartRoutineByLocalIdentifierPositiveResponse 30/Nov/2013 03:19:43.694: LOG: Sent message with service ID RequestRoutineResultsByLocalIdentifier 30/Nov/2013 03:19:43.722: LOG: Received message with service ID RequestRoutineResultsByLocalIdentifierPositiveResponse 30/Nov/2013 03:19:43.722: LOG: Checksum is correct. 30/Nov/2013 03:19:43.723: USER: Flash checksum matches new data, flashing is unnecessary, but flashing anyway. 30/Nov/2013 03:19:43.723: USER: Requesting flash memory erase for address range 0x00800000 to 0x00803FFF. 30/Nov/2013 03:19:43.726: LOG: Sent message with service ID StartRoutineByLocalIdentifier 30/Nov/2013 03:19:43.756: LOG: Received message with service ID NegativeResponse 30/Nov/2013 03:19:43.756: LOG: Received negative response for service ID: StartRoutineByLocalIdentifier, with response code: RoutineNotCompleteOrServiceInProgress 30/Nov/2013 03:19:43.756: USER: ECU reports routine not complete while attempting to erase flash memory. 30/Nov/2013 03:19:45.484: LOG: User Prompt - Title: Sector Erase Failed Message: Failed to erase the memory sector. Press OK to skip this sector and continue, or Cancel to abort the flashing process. Result: OK 30/Nov/2013 03:19:45.484: USER: 2% complete. 30/Nov/2013 03:19:45.485: USER: Starting to flash data block. 30/Nov/2013 03:19:45.485: USER: Calculating flash checksum to determine if flashing is necessary for range: 0x00804000 to 0x00806000 30/Nov/2013 03:19:45.485: LOG: Validating flashed data checksum for address range 0x00804000 to 0x00805FFF. 30/Nov/2013 03:19:45.488: LOG: Sent message with service ID StartRoutineByLocalIdentifier 30/Nov/2013 03:19:45.514: LOG: Received message with service ID StartRoutineByLocalIdentifierPositiveResponse 30/Nov/2013 03:19:45.518: LOG: Sent message with service ID RequestRoutineResultsByLocalIdentifier 30/Nov/2013 03:19:45.546: LOG: Received message with service ID RequestRoutineResultsByLocalIdentifierPositiveResponse 30/Nov/2013 03:19:45.546: LOG: Checksum is correct. 30/Nov/2013 03:19:45.547: USER: Flash checksum matches new data, flashing is unnecessary, but flashing anyway. 30/Nov/2013 03:19:45.547: USER: Requesting flash memory erase for address range 0x00804000 to 0x00805FFF. 30/Nov/2013 03:19:45.551: LOG: Sent message with service ID StartRoutineByLocalIdentifier 30/Nov/2013 03:19:45.580: LOG: Received message with service ID NegativeResponse 30/Nov/2013 03:19:45.581: LOG: Received negative response for service ID: StartRoutineByLocalIdentifier, with response code: RoutineNotCompleteOrServiceInProgress 30/Nov/2013 03:19:45.581: USER: ECU reports routine not complete while attempting to erase flash memory. 30/Nov/2013 03:19:46.721: LOG: User Prompt - Title: Sector Erase Failed Message: Failed to erase the memory sector. Press OK to skip this sector and continue, or Cancel to abort the flashing process. Result: OK 30/Nov/2013 03:19:46.721: USER: 2% complete. 30/Nov/2013 03:19:46.721: USER: Calculating checksum for first sector flashed to determine which erase mode the ECU is using. 30/Nov/2013 03:19:46.721: LOG: Validating flashed data checksum for address range 0x00800000 to 0x00803FFF. 30/Nov/2013 03:19:46.729: LOG: Sent message with service ID StartRoutineByLocalIdentifier 30/Nov/2013 03:19:46.758: LOG: Received message with service ID StartRoutineByLocalIdentifierPositiveResponse 30/Nov/2013 03:19:46.763: LOG: Sent message with service ID RequestRoutineResultsByLocalIdentifier 30/Nov/2013 03:19:46.789: LOG: Received message with service ID RequestRoutineResultsByLocalIdentifierPositiveResponse 30/Nov/2013 03:19:46.790: LOG: Checksum is correct. 30/Nov/2013 03:19:46.790: USER: ECU appears to be in erase entire flash mode, restarting the flash process. 30/Nov/2013 03:19:46.790: USER: Starting to flash data block. 30/Nov/2013 03:19:46.790: USER: Requesting flash memory erase of entire flash memory. 30/Nov/2013 03:19:46.794: LOG: Sent message with service ID StartRoutineByLocalIdentifier 30/Nov/2013 03:19:46.823: LOG: Received message with service ID NegativeResponse 30/Nov/2013 03:19:46.824: LOG: Received negative response for service ID: StartRoutineByLocalIdentifier, with response code: RoutineNotCompleteOrServiceInProgress 30/Nov/2013 03:19:46.824: USER: ECU reports routine not complete while attempting to erase flash memory. 30/Nov/2013 03:19:46.824: USER: Writing ECU flash memory failed. Title: Re: Can´t erase flash memory Post by: ddillenger on November 30, 2013, 08:24:31 AM Open the ecu guy. Chances are it's not stock.
Title: Re: Can´t erase flash memory Post by: Alcazer on November 30, 2013, 08:32:19 AM But map on it is stock. I think someone then did flash it somehow anyway.
Title: Re: Can´t erase flash memory Post by: nyet on November 30, 2013, 01:22:13 PM A modified ECU can easily have a stock file on it. Open the ECU. I bet you'll find a riser in it.
Title: Re: Can´t erase flash memory Post by: Alcazer on November 30, 2013, 02:43:46 PM Thank you guys for that information!
But if it is aftermarket then there is no way to flash it ? Title: Re: Can´t erase flash memory Post by: ddillenger on December 01, 2013, 07:36:12 AM You can desolder the aftermarket chip/board, install a stock one, then flash to your hearts content. If you're not capable of soldering Id help out.
Title: Re: Can´t erase flash memory Post by: Alcazer on December 02, 2013, 01:07:00 AM Thank you for that information!
But where can I buy that chip only or I need to buy another ecu and take it from there so I will not have problems with Immobilizer? Title: Re: Can´t erase flash memory Post by: ddillenger on December 02, 2013, 01:31:27 AM You can get the chips on ebay. 29F800BB or 29F400BB depending on the year. Make sure to get 70 or faster rated.
Title: Re: Can´t erase flash memory Post by: Alcazer on December 02, 2013, 08:40:46 AM You can get the chips on ebay. 29F800BB or 29F400BB depending on the year. Make sure to get 70 or faster rated. Would this be correct one for my 2001 G-box ? http://www.ebay.com/itm/AM29F800BB-90SC-Brand-new-FLASH-EPROM-PSOP44-SOP44-/321236419890?pt=UK_BOI_Electrical_Components_Supplies_ET&hash=item4acb2ec532 Thank you very much for help. Would love to pay you and let you do it but I´m too far from you. (in Estonia) Title: Re: Can´t erase flash memory Post by: ddillenger on December 03, 2013, 06:28:08 AM The memory speed of that chip is too slow! Needs to be 70ns or faster. 29F800BB-70SD are what I use.
|