Eprom ID

n01tk · Post by **n01tk** » Wed May 18, 2011 6:02 am

I checked Eprom ID under scalars. I don't think I am opening up the location properly. It shows all zeros and states sixteen bits but doesn't appear active. I am connected to the ECU & all data is active. When I go over to the left hand side and open scalars a long list appears. One of the scalars ( about half way down) is the Eprom ID. What do I do with it? I tried right and left mouse click. Doesn't show me whats in that location.
_________________

Post by **robertisaar** » Wed May 18, 2011 7:47 am

PROM ID can be used to identify a tune without necessarily knowing what the BCC of it is.

it should show values other than just 0s though...

sounds like you might have the wrong XDF for whatever BIN you're playing with.

EagleMark · Post by **EagleMark** » Wed May 18, 2011 8:06 am

robertisaar wrote:PROM ID can be used to identify a tune without necessarily knowing what the BCC of it is.

it should show values other than just 0s though...

sounds like you might have the wrong XDF for whatever BIN you're playing with.

Or someone has changed it to all 0s ?

Post by **robertisaar** » Wed May 18, 2011 8:14 am

also a possibility.

not sure why someone would do that, but i've seen it before.

EagleMark · Post by **EagleMark** » Wed May 18, 2011 8:16 am

robertisaar wrote:also a possibility.

not sure why someone would do that, but i've seen it before.

I agree! But the only thing I can think of why someone would change to all 0s instead of leaving it alone or changing to their version number is they thought it was a checksum that needed to be disabled for some reason?

Post by **robertisaar** » Wed May 18, 2011 8:20 am

PROM ID is in no way related to checksum functions though...

n01tk: when you connect via the datastream, if you have a PROM ID value in the stream(some, especially the flash modules, do not), it SHOULD match the value that is stored in the BIN.

EagleMark · Post by **EagleMark** » Wed May 18, 2011 9:51 am

robertisaar wrote:PROM ID is in no way related to checksum functions though...

I know now! But made that mistake and have seen others make that mistake...

Guess the point is that chip he has is NOT a factory bin file.

Post by **robertisaar** » Wed May 18, 2011 10:00 am

or a corrupt BIN, or possibly an incorrect XDF.

those are about the only possibilities i see.

EagleMark · Post by **EagleMark** » Wed May 18, 2011 10:03 am

robertisaar wrote:or a corrupt BIN, or possibly an incorrect XDF.

those are about the only possibilities i see.

Yeah my bad I forgot about that...