RomRaider

On the left 'ROM Info' view it shows 'sti04' so it is somehow not using definitions that are shown on your notepad... check that in 'Edit -> Settings' you have EcuFlash definition dir set where those files are or copy them to location pointed in settings and check that you don't have duplicate definition in any folder under definition folder.

hmm, strange, I specified the definitions folder, checked that there were no duplicates. however, the flash method in the ROM information remained the same sti04

I would say that you have somewhere def file for that ROM with flashmethod sti04. I tested it and it start with using fxt02 method and shows it under ROM info too.

writing ROM without reading it worked)) I still didn’t understand what I did, but there were no repeating definitions.

even with active map editing, the program sometimes hangs, and you have to close it and open it again, the data is not saved. the speed limit in ecuflash is displayed correctly, and in fastecu, instead of a dot value, the point, as well as the advance multiplier

off topic question, does ecuflash correct checksums?

Ok, I will look for those bugs, thanks!

And yes, EcuFlash will correct checksums.

Fixed definition parsing bug. Hope I didn't brake anything else

Can you tell in what cases software hangs, so I can try to test it to find cause to it? And it doesn't crash, it just hangs?

I will later add it to use temp files for maps, so they can be recovered in case of hanging or crashing.

I edited the ignition map, one cell at a time and quickly, and the program hung. Windows prompts you to end the process. or when several cells at once. I also noticed that the value changes only from the second time. I change the value, I press Enter, but it remains the same, I change the value again, Enter, and it changes on the map

Hmmm... tested with Linux and Win7 64bit in VM but didn't noticed those... no matter how fast I change map cell values or keep +/- pressed it won't hang. Sometimes, if changing value with +/- it might not change at first click due to system how it calculates ROM value, but I'm fixing that. Changing value(s) with 's' is working every time in my environment.

What ROM, Windows version and machine are you using?

2A04446505_A8AK212A, win7 32bit.

I didn’t understand what kind of “machine” we are talking about?

Meaning what kind of PC are you using? I will test later also with Win7 32bit as soon as I get that laptop back from friend.

Lenovo z575

Did some testing in Win7 32bit and Acer Acpire One 722 and only way I could reproduce hanging problem was setting +/-/* with zero value so it stucks in loop. Will fix it later today.

where can i find the full definition for my a8ak212a rom? i read the topic about creating with IDA, but I already blunted at the stage when I found the ecu id, and then I didn’t figure out what to do, I’m an expert in another direction) maybe there is a person who will help, for a fee) I’m interested in enrichment during startup and warm-up and how to disable af#3 correction and rear o2

can you do support ecu Processor m32 M32176F4 MH8302F ?
ecu id 2F04207006
2F04207106
2F04207206
2F04207306
3C04203006
3C04207006
legacy bl5 jdm ej204