Help Identifying a bin

[Lawso]

I have had a car arrive to tune. It's running an 808 ecu that has been previously been played with.
The car has multiple issues, so I decided to read the bin of the memcal to try to see what had been done.

After trying with a number of XDF's I have been unable to read the bin.

I opened it with a hex editor, and in the last row of the bin, it says OSE12Pro Flash OSE12Pro Prog.

I tried using the ose xdf, but maybe this bin was created with an earlier version or it may be corrupted?

If anyone can suggest which XDF to use I would appreciate it. A copy of the bin is attached.

[vlt304]

looks incomplete in hex was it on a nvram or eprom? did you read it with a burner or the flash tool?

[Lawso]

I used the burner to read the eprom. The car was running but poorly, so maybe it was corrupted?

[Holden202T]

if you split the bin file into two 32kb's one is blank and the other looks reasonably like a $12P tune, but i am not sure what version.

[antus]

Its definately corrupted.

EG The line at 9FF0 should say "OSE12PRO ALDL" but contains "OWE56Tvo$ELDL..." and the last 3 . are the version number in hex. Each OSE section header has it. Should be 111 but in this case its 555 for the ALDL section header.

The sections at the end of the file have version 111 but the earlier part of the chip is bad.

[antus]

The code section at the end seems to be OK, but I think the original user might have had a problem with the data pin for binary '4' when they read the cal area and merged it with the code section. All the 4 bits are set in the cal area, so those values where that bit should be 0 have been corrupted by adding a value of 4.

0+4=4 and Version 111 + 444 = 555

[Lawso]

Thanks for the help. Makes sense now.

Was planning to tune it from scratch anyway, but it is interesting to see why it may have been having issues.

[Dylan]

Maybe you coud dig out there spark and VE still from hex? See how it compares to yours afterwards.

[Lawso]

I''ll just tune it again. Have to do some training with this one anyway, so it was interesting to come across a corrupted file. A good learning opportunity.

[BennVenn]

It is more likely there is a break on the data line, I/O2 as this left floating will float high and logically OR 0x04 with all data on the chip. This can be verified by the fact at all lower nibble values are either 5,4,6,7,C,D,E or F. Take a look for a bad solder joint or break on pin13 of the EPROM/Memcal.