openecu.org

Got an EC*t*k'd ECU, pulled the ROM and rain through XMLWrite V6.

When I open it in Enginuity as a 160K ROM, there are errors saying that some parameters are out of bounds.

So, I convert the image to 192K and run it again, there are fields that apparently enable disabling sensors. (I'm specifically interested in diabling the TGV system)
Only problem is that it's obvious the code is lost because the values are wacky.

Wondering if there's a way to pull the entire 192K region?

-Jason

the ROM is only 160k. the 192k format just adds a 32k "space" between the lower 128k and the upper 32k.

cboles wrote:the ROM is only 160k. the 192k format just adds a 32k "space" between the lower 128k and the upper 32k.

That's my point, XML Write seems to think there's code in that space with vendor solutions for CELs and functionality.

I guess my question is what is in that space in the ECU firmware?

-Jason

XML Write doesnt think at all yet

Just to be sure, there are 2 format:
160 K and 192 K

One contains RAM space (192K), filled with null values, whereas the other one not.

XML write handles dump in 192K format. But you can be sure that no tuning data are available in the ram area (the 32k available between the first 128K ROM block and the second 32K ROM block)