NefMoto

i have a problem flashing my a-box ecu that already has m-box software from AWE.
im using cable FT232R
i can read ecu info and codes, i also saved a copy of the .bin file from my current tune.

but when i try to flash with normally it fails flashing one sector at a time. then i select erase entire memory and it tries but i get this message over and over in the log file.
8: USER: Truncated log file because it was larger than 10 megabytes.
10/Mar/2011 01:24:32.872: LOG: Received negative response for service ID: RequestRoutineResultsByLocalIdentifier, with response code: RoutineNotCompleteOrServiceInProgress
10/Mar/2011 01:24:32.874: LOG: Sent message with service ID RequestRoutineResultsByLocalIdentifier
10/Mar/2011 01:24:32.886: LOG: Received message with service ID NegativeResponse
10/Mar/2011 01:24:32.888: LOG: Received negative response for service ID: RequestRoutineResultsByLocalIdentifier, with response code: RoutineNotCompleteOrServiceInProgress
10/Mar/2011 01:24:32.889: LOG: Sent message with service ID RequestRoutineResultsByLocalIdentifier
10/Mar/2011 01:24:32.907: LOG: Received message with service ID NegativeResponse
10/Mar/2011 01:24:32.907: LOG: Received negative response for service ID: RequestRoutineResultsByLocalIdentifier, with response code: RoutineNotCompleteOrServiceInProgress
10/Mar/2011 01:24:32.909: LOG: Sent message with service ID

also here is my current awe ecu tune

Can you post the full log file? If you go to the file menu in the flashing software you can find the log file.

nothing to say about the flashing but take a look at
kvb, fuel consumption constant for display, looks low for a 630cc setup... is that because you are running a 3 bar fpr?

also looks like you could add some timing up top (higher rpms) if you wanted, in kfzw2
not sure what octane you run though. if it's 93 then definately, if it's 91 just a little.

i am using a 3 bar fpr and i havent touched the kvb map except with vagcom which can only go so far.

Is it flashed or a socketed chip?

The log was truncated because it was too long, so it doesn't show anything useful.

Do you know how far it got flashing the entire chip at once?

Can you try flashing again and save the log file before it overflows and gets truncated?

this is what it said..

Disabling Windows sleep mode.
Writing ECU flash memory.
Fast writing premium feature NOT enabled.
Reading ECU identification option: calibrationEquipmentSoftwareNumber
Read ECU identification option with unknown scaling record.
Successfully read ECU identification information
ECU reports programming session preconditions have been met.
Requesting security access.
ECU reports that security access is not supported.
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.
Memory layout is valid.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00800000 to 0x00810000
Flash checksum does not match new data, flashing is necessary.
Requesting flash memory erase for address range 0x00800000 to 0x0080FFFF.
Erase flash memory routine did not start or complete correctly.
Skipping flash sector and continuing flashing process.
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.
Data transfer failed.
100% complete.
Writing ECU flash memory failed.
Restoring Windows sleep mode.
Disconnecting because no response was received for the Tester Present message.
Disconnected

 i dont think it did anything be cause i just took my car to the store so the ecu is not bricked yet.lol

Do you have the log file for that flashing attempt?

here is the log for a recent attempt.

So this log shows that you skipped flashing the first sector, and then the second sector failed to write properly. Have you ever tried the "erase entire flash" option instead of skipping the sector?

i did the first time i tried but this is my only ecu and working car so i cant afford for it to mess up.

do you think my cable is bad? it wont read from vagcom anymore since i installed the nefmoto software and cmd driver.

FOUND MY PROBLEM... >:(
(http://i413.photobucket.com/albums/pp212/cj5470110/031701_204700.jpg)
This is y i cant flash a new file. anyone have a stock m or a box ecu?

i took the chip off the board being a curious dumbass and when i put the ecu back into my car i have fuel injector 1 open circuit  :'(  car ran on 5 cylinders all the way home from work. i must have fried something with static discharge i dont know if its the ecu or the injector which only has 3000 miles on it.

on second thought i think i could have bent the top left pin slightly on the socketed chip so its not getting a good connection. i pulled the ecu back out and reseated the chip and it ran fine for 50 miles then started firing on only 5 cylinders again

That is why I asked at the beginning.

I  have stock mbox ecu on the way to me now. hopefully soon then i can flash my car

Awesome, glad you figured it out. I was going a little crazy wondering what was up with your ECU. Version 1.7.0.0 should be very stable, and what you were reporting wasn't making sense.