checksum question

[upyas]

i cant use the flash tool on the realtime ecu, i did try

wrongflash.jpeg

[upyas]

i am not using the ostrich with this issue, i am just trying to write the tune file to a normal ecu, if i use a eprom programmer with the same tune file the ecu boots and works correctly, its only when trying to write bins on ose flash tool that i get the checksum question.

weirdly it does not actually brick the ecu every time, a few times i was able to write as normal and the ecu rebooted as expected, even with the same file!

He is using an ostrich with an adapter soldered to the board (hopefully he shares the video).

I wonder if that is what is causing the problem?

[pman92]

He is using an ostrich with an adapter soldered to the board (hopefully he shares the video).

Oh cool.

Looking at your screenshot it must be because you're using the ostrich, and it's not detecting whatever type of flash chip the standard ECU uses.

[upyas]

i am having this problem when trying to write tune files to a ecu using a aldl cable and the ecu is stock.

i just posted that pic to show what happens when you try and use OSE flash tool with the emulator

what i do not understand is that sometimes it works, i have been able to put the tune into a ecu a few times with no issues, also if i write the tune to the chip directly and put it in the ecu it works fine also.

[antus]

Is it a different type of chip to stock that the programmer supports but is not the oem flash when ose plugin tries to write it?

[delcowizzid]

Read the stock ecu copy the tables you modified over to it from your tuned file tick auto fix checksum and flash it

[Rhysk94]

Tick the autofix checksum.
I literally posted a link to a video showing how to do it all so you never brick a pcm again.

[upyas]

hey mate, i do that every time before i connect to the ecu.

[Rhysk94]

If its ticked, there shouldn't ever be a box pop up to do with checksum's
Something weird is happening.

Possibly remove the oseflash tool program completely amd try a fresh install.
Potentially windows has corrupted something in an update, like they did with the G4X programmers on win 11 haha