NefMoto

Technical => Flashing and Chipping => Topic started by: coreyj03 on April 29, 2011, 05:35:17 AM



Title: recent flash attemps with new cable successfully complete but are bad.
Post by: coreyj03 on April 29, 2011, 05:35:17 AM
i let someone borrow my original cable so now im using a 232BL  ive tried all 3 memory layouts and have been successful with only 3 flashes but every time it turns out to be corrupt and wont start.

i attached the log. anyone know whats going on?  o and this is a t box ecu that im flashing with m box software


Title: Re: recent flash attemps with new cable successfully complete but are bad.
Post by: Tony@NefMoto on April 29, 2011, 05:43:04 PM
It seems like some of the message responses are coming back corrupted.

Are you sure the ECU voltage is a solid 12v?

You may want to see if reducing the latency settings in the serial port settings in the device manager of the control panel gives you any improvements.


Title: Re: recent flash attemps with new cable successfully complete but are bad.
Post by: coreyj03 on April 30, 2011, 07:41:00 PM
i have above 12v on the guage and have never had problems before... now tonight i tried to flash with my normal cable and i get a more consistent 100% flash but still same BS a corrupt falsh.

i lowered the latency 2 different times  and also changed different versions of FTDI drivers  

but the ecu is still logging that "Service ID Received Negative Response"   but it flashes all the way through. what does that mean?

i pulled the ecu apart and it has the 800BB memory layout.

here is tonight's logs


Title: Re: recent flash attemps with new cable successfully complete but are bad.
Post by: coreyj03 on May 01, 2011, 07:36:03 PM
found out the problem,..  somehow my tune is corrupt and wont start the car. i flashed your base file and it works , but idle is very poor probably due to me having e85. but i will adjust accordingly :)


Title: Re: recent flash attemps with new cable successfully complete but are bad.
Post by: Tony@NefMoto on May 04, 2011, 07:26:26 PM
Glad you sorted your problems out. There are normally negative responses when flashing the ECU. Looking at your latest log file I didn't notice anything that looked bad. Was there a specific entry in the log file that you were concerned about?

I did noticed one bug in your first log file. When the program decided to truncate the log file because it was larger than 10 megs, that caused a 5 second stall, and you lost connection to the ECU. I will have to fix that. Thanks for sending me the log where that happened.