NefMoto > Technical > NefMoto Software > Sector erase fail while flashing 94%
Pages: [1]
« previous next »
Author Topic: Sector erase fail while flashing 94%  (Read 12853 times)
seany260
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 119
« on: April 15, 2017, 12:11:24 AM »
Having this issue with windows 8 x64 computer, works fine on my windows 7.
Any idea why it would do this at 94%.

It has this issue everytime I try to flash for the first time, when I select 'yes' at this point to erase completely, it flashes entire file again and finishes. Never seen this on my 32bit windows 7 computer and it's a real pain in the arse.
« Last Edit: April 15, 2017, 06:50:02 AM by seany260 » Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12268


WWW
« Reply #1 on: April 15, 2017, 01:06:17 AM »
Logged
ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
aef
Hero Member
*****

Karma: +69/-46
Offline Offline

Posts: 1600
« Reply #2 on: April 15, 2017, 01:07:11 AM »
Small picture is small

Maybe difference in baud rate? Post whole log of nefmoto instead of picture. post both logs, win7 and win8.
Logged
seany260
Full Member
***

Karma: +0/-1
Offline Offline

Posts: 119
« Reply #3 on: April 15, 2017, 06:44:31 AM »
  Cheesy Cheesy Cheesy
new and improved picture, here is a log of the last flash, stopped at 98% this time, I just selected no too not overwrite  and skip. car starts ok.
cant do windows 7 as my other computer is scrap!

Code:
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected
Disabling Windows sleep mode.
Writing ECU flash memory.
ECU reports programming session preconditions have been met.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Validating flash memory starts at 0x00800000 and ends at 0x00900000.
Validation failed, ECU reports that security access is not granted.
Memory layout validation failed.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00800000 to 0x00810000
Flash checksum matches new data, flashing is unnecessary, skipping.
6% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00810000 to 0x00820000
Flash checksum does not match new data, flashing is necessary.
Requesting flash memory erase for address range 0x00810000 to 0x0081FFFF.
Successfully erased flash memory.
Requesting download to ECU for address range 0x00810000 to 0x0081FFFF.
Request download to ECU succeeded.
Starting data transfer.
7% complete.
8% complete.
9% complete.
10% complete.
11% complete.
12% complete.
Data transfer complete.
Requesting data transfer exit.
Successfully exited data transfer.
Calculating flash checksum to determine if flashing was successful for range: 0x00810000 to 0x00820000
Flash checksum matches new data, flashing was successful.
Calculating checksum for first memory range to determine which erase mode the ECU is using.
ECU appears to be in erase sector mode, continuing the flash process.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00820000 to 0x00830000
Flash checksum does not match new data, flashing is necessary.
Requesting flash memory erase for address range 0x00820000 to 0x0082FFFF.
Successfully erased flash memory.
Requesting download to ECU for address range 0x00820000 to 0x0082FFFF.
Request download to ECU succeeded.
Starting data transfer.
13% complete.
14% complete.
15% complete.
16% complete.
17% complete.
19% complete.
Data transfer complete.
Requesting data transfer exit.
Successfully exited data transfer.
Calculating flash checksum to determine if flashing was successful for range: 0x00820000 to 0x00830000
Flash checksum matches new data, flashing was successful.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00830000 to 0x00840000
Flash checksum matches new data, flashing is unnecessary, skipping.
25% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00840000 to 0x00850000
Flash checksum matches new data, flashing is unnecessary, skipping.
31% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00850000 to 0x00860000
Flash checksum matches new data, flashing is unnecessary, skipping.
38% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00860000 to 0x00870000
Flash checksum matches new data, flashing is unnecessary, skipping.
44% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00870000 to 0x00880000
Flash checksum matches new data, flashing is unnecessary, skipping.
50% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00880000 to 0x00890000
Flash checksum matches new data, flashing is unnecessary, skipping.
56% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00890000 to 0x008A0000
Flash checksum does not match new data, flashing is necessary.
Requesting flash memory erase for address range 0x00890000 to 0x0089FFFF.
Successfully erased flash memory.
Requesting download to ECU for address range 0x00890000 to 0x0089FFFF.
Request download to ECU succeeded.
Starting data transfer.
57% complete.
58% complete.
59% complete.
60% complete.
61% complete.
62% complete.
Data transfer complete.
Requesting data transfer exit.
Successfully exited data transfer.
Calculating flash checksum to determine if flashing was successful for range: 0x00890000 to 0x008A0000
Flash checksum matches new data, flashing was successful.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x008A0000 to 0x008B0000
Flash checksum matches new data, flashing is unnecessary, skipping.
69% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x008B0000 to 0x008C0000
Flash checksum matches new data, flashing is unnecessary, skipping.
75% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x008C0000 to 0x008D0000
Flash checksum matches new data, flashing is unnecessary, skipping.
81% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x008D0000 to 0x008E0000
Flash checksum matches new data, flashing is unnecessary, skipping.
88% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x008E0000 to 0x008F0000
Flash checksum matches new data, flashing is unnecessary, skipping.
94% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x008F0000 to 0x008F8000
Flash checksum matches new data, flashing is unnecessary, skipping.
97% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x008F8000 to 0x008FA000
Flash checksum matches new data, flashing is unnecessary, skipping.
98% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x008FA000 to 0x008FC000
Flash checksum matches new data, flashing is unnecessary, skipping.
98% complete.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x008FC000 to 0x00900000
Flash checksum does not match new data, flashing is necessary.
Requesting flash memory erase for address range 0x008FC000 to 0x008FFFFF.
Erase flash memory routine did not start or complete correctly.
Skipping flash sector and continuing flashing process.
100% complete.
Disconnecting from ECU to force it to recognize successful completion of flash write.
Writing ECU flash memory succeeded. Wrote 18 of 19 sectors in flash memory.
Flashing time was 00:02:25.
Restoring Windows sleep mode.
Disconnecting...
Disconnected
Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12268


WWW
« Reply #4 on: April 15, 2017, 09:24:58 AM »
it says 100% there
Logged
ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
k0mpresd
Hero Member
*****

Karma: +146/-54
Offline Offline

Posts: 1655
« Reply #5 on: April 15, 2017, 09:28:11 AM »
Quote from: nyet on April 15, 2017, 09:24:58 AM
it says 100% there

you did not read log fully. log says attempting to erase last sector, failing, and then showing 100%. flash is incomplete.

even says 18 out of 19 sectors at the last part of log.
« Last Edit: April 15, 2017, 09:30:25 AM by k0mpresd » Logged
buchdich
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 8
« Reply #6 on: October 02, 2017, 04:23:55 PM »
did you ever figure this out i am having the same issue. do you get any checksums when  you read the file
Logged
milopl81
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 4
« Reply #7 on: October 14, 2017, 03:42:29 AM »
I have the same problem ... stop on 94% and second flashing process complete. Huh

More detail from my side : http://nefariousmotorsports.com/forum/index.php?topic=2200.msg108156#msg108156

nyet take off the pink glasses and you will see ...   Tongue
Logged
milopl81
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 4
« Reply #8 on: October 15, 2017, 07:34:19 AM »
I solved this issue but i have not a green idea where was the problem.

If you have this problem reinstall OS , drivers /cable/ and app nefmoto software.  /  this help for me. /

If it is not possible on your PC install VM Virtual BOX and install all on virtual host and check it.  It should help.
Logged
gareth_iowc
Full Member
***

Karma: +1/-1
Offline Offline

Posts: 62
« Reply #9 on: October 19, 2017, 05:20:36 AM »
use the MPPS cable and software
Logged
Pages: [1]
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • November 22, 2024, 01:08:36 PM
  • Welcome, Guest. Please login or register.
    Did you miss your activation email?

    Login with username, password and session length
Search
 
Advanced Search
About Disclaimer
All Rights Reserved 2010 Nefarious Motosports
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.032 seconds with 17 queries. (Pretty URLs adds 0.001s, 0q)