Identify unknown VR 424 BIN

[pman92]

Is anyone able to identify the attached file?

I'm told it from a VR V8 Auto (424 ecu).
It was tuned many years ago (maybe with that thing starting with K?)
I need to disable some error codes on it.

Memcal ID tool doesn't know what it is.
There are a few chunks of data (maybe tables?) that are identical to $11, but they are at different memory offsets.

Thanks in advance

[antus]

Not really sure, but it looks sort of like a modified version of something starting with C rather than K, and that won't help you any. You'll probably need to ID tables by pattern and move the data you need out and into 11P by hand. The 'C' bins that I have seen do share a reset vector of 80 11 that matches this, and a copyright message this does not have. But the data is still shuffled around from my sample compared to this, so it's a very loose association at best. it could just as easily be yet another individual's version of a modified $11.

[VX L67 Getrag]

Sorry to jump in on this but yeah I did have a look yesterday & didn't think it started with a "K" but couldn't spend too much time to find more about it & yeah I didn't see the copyright section... But to ask a question about what is mentioned what does the reset vector of 80 11 mean?

[antus]

Its the number in the last 2 bytes of the bin. Its where the processor looks when it boots up, then it jumps to that address to start executing. You'll find it's different in most operating systems, it's just co-incidence where it ends up when the bin is assembled or compiled, but I just thought it was a noteworthy similarity because even though it doesn't prove the code is the same (or even related), if someone just stripped the copyright notice that hint about similarity might have been left behind. I've got 2 other bins that have reset vector 80 11 and they're both from the one aftermarket place. Vectors are addresses, in a documented location in the datasheet of the processor. Most but not all platforms have vectors somewhere that the CPU datasheet describe, and when reverse engineering looking for a vector table and starting to disassemble from the reset vector (address) is usually the first thing to do. (then you also consider interrupt vectors, or any other vectors that hardware uses to run something)

[VX L67 Getrag]

WOW thats cool, thank you very much for taking the time to explain!

[pman92]

The customer ending up looking further into this. Looks like a lot of it lines up with $11 using a negative 0x1000 offset

[delcowizzid]

There is more than 1 xdf for vr v8 auto stuff a d it messes up the tables if you use the wrong version

[pman92]

There is more than 1 xdf for vr v8 auto stuff a d it messes up the tables if you use the wrong version

Yes I told him to be careful. I think he's going to get a programmer so he can trial and error it himself.
He just wants a couple of flags flipped to disable some DTCs, and with the offset applied and comparing the flag locations in hex editor, all the surrounding data seems to be a match. So I think it will be correct, but we will wait and see.

[antus]

yes there is 3. there are only a couple of bytes if that between them, from the offset where the change was made only. 0x1000 offset is custom, plus probably other unknown changes too. but data order is a very useful characteristic to help figure it out.