Radio code location in memory dump from Alpine MF2199

[zdzich]

After analyzing the dump thanks to the response from SITI I found that the radio code was located in address 00000010 which is the second line from the top. In my situation it was 73570.
First five lines of the memory:
28 98 98 07 17 00 00 98 00 FF FF FF FF FF FF FF
07 35 70 43 07 35 70 43 F8 CA 8F BE 0B 00 FF FF
03 44 04 59 03 05 02 01 04 D2 43 20 17 00 00 00
A8 D2 42 20 07 00 00 00 CA D2 41 60 56 00 00 00
75 D1 33 20 01 00 00 00 00 D1 42 20 02 00 00 00

So, if anyone needs to find the code first try to read the memory dump from your radio. It is a good chance that you will find it where I did in my radio.

[bonus2010]

Thanks for sharing this information. The fact is, I was
very near to agreeing with fellow member that it was a
bad dump, because the lines you've shown is not what
you uploaded. When I saw the code had been extracted I put
it down to possibly a different version of the MF2199 that
I've not come across.

From downloading your attachment I got this:-

00x10 4E 73 D5 00 00 00 00 02 00

Obviosly SITI has been very clever here, being able to
manipulate this data in some way.

And.. most probably limitations in my own knowledge in this.

If experienced decoders can put me right on this, would be very
grateful.

Cheers.

[alexics]

Thanks for sharing this information. The fact is, I was
very near to agreeing with fellow member that it was a
bad dump, because the lines you've shown is not what
you uploaded. When I saw the code had been extracted I put
it down to possibly a different version of the MF2199 that
I've not come across.

From downloading your attachment I got this:-

00x10 4E 73 D5 00 00 00 00 02 00

Obviosly SITI has been very clever here, being able to
manipulate this data in some way.

And.. most probably limitations in my own knowledge in this.

If experienced decoders can put me right on this, would be very
grateful.

Cheers.

Siti has been clairvoyant as the data you posted from your download was wrong. zdzich posted the correct data above. I assume the radio had to be dumped again. The important thing is it was solved. That's why I appreciate the spirit of this forum.

[zdzich]

no, I didn't have to dump the radio, just put it back in the car and it worked fine.

[bonus2010]

no, I didn't have to dump the radio, just put it back in the car and it worked fine.

We refer to a 'dump' as the memory contents of the
security eeprom chip.

I've very very recently discovered that the 'dump' can
be provided in different formats. The dump that you
originally posted was in a different format to what I
would normally be able to recognise.

Ok I know dump's got other meanings as well.....

[zdzich]

it was in bin format, the format that my eprom programmer uses. you would have to connect your eprom programmer and then open the file to read it.

[bonus2010]

it was in bin format, the format that my eprom programmer uses. you would have to connect your eprom programmer and then open the file to read it.

You don't need an eprom programmer to view a bin file.
Every piece of data you can think of that is recognisable
by computers is and only is in binary format.

However, every application has it's own methods of storing
data. These ways of storing data, all in binary format can
include additional information, which is only recognisable
by that specific application software.

For example, I've just recently learnt that Polyprog stores
data in a particular way - probably including data that is
only recognisable by that application - and should that data
be uploaded by an independant raw binary data analyser - would
just appear nonsence.

All eeprom applications have an option to store data
in raw binary format, that's excludes any additional
proprietry information being attached to the file.

Thanks for your post, been doing a bit of learning through this...

Cheers.

[zdzich]

I agree, but when you have a programmer connected to the eeprom in the radio it is very convenient to view the dump at that time. thanks for your comments.