NefMoto

Hello,

I have a question, why so great was the difference in writing between these two files?


(http://img714.imageshack.us/img714/4913/pantallagticor2b.jpg) (http://imageshack.us/photo/my-images/714/pantallagticor2b.jpg/)

Uploaded with ImageShack.us (http://imageshack.us)

(http://img7.imageshack.us/img7/3554/pantallagtijuli.jpg) (http://imageshack.us/photo/my-images/7/pantallagtijuli.jpg/)

Uploaded with ImageShack.us (http://imageshack.us)

Hard is the same, same notebook and same cable .-

TNKS A LOT 4 HELP!

I had the same problem and posted this question in the NefMoto Flasher 1.8.0.0 download thread.  Haven't yet received a response.

http://nefariousmotorsports.com/forum/index.php/topic,691.msg7137.html#msg7137

Someone can help with this question? :o :o :o

Thanks! ;D

 ??? ??? ??? ??? ??? ??? ???

are they both 1MB files?  do either of them have multiple maps (w/ switching capability)?

Yes, is the same file.- :S

sorry if im inthe wrong but hopefully both can be answered.. i have flashed a file 2 times now and both times it has wrote 19 of 19 sectors. Any one know why that is?Most say its 16 of 16 but i get 19 of 19 ?

First of all you're showing flash times for two different files, you can hardly call it the same condition...

Tony's software doesn't flash a block from BIN file that has nothing in it and skips if over saving you time. It still registers that block as "flashed" though. If the other file has data/code in the same area the other file has nothing, it will take much longer to flash.

I am pretty sure this would account for timing discrepancies.

Memory Layout 29F800 (16 sectors) vs 29F800BB (19 sectors).

Also, if you use the 29F800 layout on a 29F800BB chip, your write time will take over an hour, and I'm pretty sure will brick the ECU.  Ask me how I know.  The wiki page for supported ECUs is not correct stating that some ECUs are 29F800 when they should be 29F800BB.  Best way to tell is to just open the ECU and look at the label on the chip.

Can you post a log file of the flash that took over an hour?

Which memory layout file were you using?

I have attached my full log file below.  The following timestamps represent the start and finish of the 1+ hour flash:
START - 30/Jul/2011 01:22:35
END - 30/Jul/2011 02:37:44

Throughout the entire log file attached, I was using the "ME7 29F800.MemoryLayout.xml" as directed by the Supported ECUs wiki page.  I was having no issues reading bin files from the ECU.  But writing took over an hour. I noticed that my ECU had a 29F800BB chip inside, so I changed the memory layout to "ME7 29F800BB.MemoryLayout.xml" had I have not had an issue with writing since.  The 29F800 and 29F800BB layout files appear to be very different.  16 sectors vs 19 sectors, and different sizes.

I should mention that after the 1+ hour write session in the timestamps above, I had a bricked ECU, but I am unsure whether or not this was because of a bad checksum.

I updated the wiki page to reflect 29F800BB for my ECU.

Thanks for posting the log file.

I don't see any errors occurring in the flashing log, and the ECU seemed perfectly happy with finishing the flashing process. Normally if there is any error in the memory layout or the ECU is at all unhappy with the amount or address of the data being written you will see negative responses from the ECU. One thing I did notice is that there was about a one and a half second delay from when the software received a TransferDataPositiveResponse until it sent the next TransferData message. There should only be a delay of 25 ms or something, not one and a half seconds. So it appears as though the really long flashing time is being caused by the NefMoto software and not the ECU, unless the ECU has requested some strange timing limits.

Were you using maximum baud or 10400 baud? Were you always flashing after connecting with slow init, or did you start using fast init? Is there anything else you changed as well when you began using the 29F800BB layout?