BMW M3 Forum
BMW M3 Forum BMW M3 Gallery BMW M3 Reviews BMW M3 Social Groups BMW M3 Chat M3Forum Sponsors >>
Loading


Mobile M3forum
Go Back   BMW M3 Forum.com (E30 M3 | E36 M3 | E46 M3 | E92 M3 | F80/X) > BMW M3 Discussions > E46 M3 (2001-2006) > Coding and Tuning
Tire Rack Buy Winter Tires Now!
Not a member? Register Now!
Register Gallery All Albums Garage Search Today's Posts Mark Forums Read Calendar FAQ

Coding and Tuning Discuss all avenues of coding and tuning here!


Reply
 
Thread Tools Display Modes
Old Wed, Jan-13-2016, 10:26:09 PM   #1
t3ddftw
Registered User
 
t3ddftw's Avatar
 
Join Date: Oct 2013
Posts: 683
In the garage:
Reputation: 0 t3ddftw is on a distinguished road
Location: Las Vegas

United States




Default MSS54HP EWS Virginization via BDM

Hey guys!

Recently purchased a BDMBlock from tap so that I could wipe the EWS ISN table from my new-to-me DME but I have a few questions before I go at it.

It's an MSS54HP running DME Program 7842981.


1. I was told that I should clear 0x3FE4 to 0x7FFF in the slave EEPROM as that is where the ISN is stored. Is that correct?

2. If 1. is true, will this impact the AIF or will I have to re-flash any data to the DME after I clear this portion of memory?

3. To define 'clear' - should I write 0x00 or 0xFF to the aforementioned area of ROM?

Thanks guys!
__________________
2006 M3 ZCP 6MT Interlagos Blue on Cinnamon interior

Mods
Engine: Full Beisan Systems VANOS rebuild
Transmission: CDV Delete
Exterior: Smoked Corners | Black Side & Kidney Grills | Painted Reflectors


My Build/OCD thread
Jump to top t3ddftw is offline   Reply With Quote
Sponsored Links
Register now and remove these ads
Old Thu, Jan-14-2016, 09:02:01 AM   #2
cossie1
Registered User
 
Join Date: Dec 2013
Posts: 436
Reputation: 0 cossie1 is on a distinguished road

United Kingdom




Default Re: MSS54HP EWS Virginization via BDM

Quote:
Originally Posted by t3ddftw View Post
Hey guys!

Recently purchased a BDMBlock from tap so that I could wipe the EWS ISN table from my new-to-me DME but I have a few questions before I go at it.

It's an MSS54HP running DME Program 7842981.


1. I was told that I should clear 0x3FE4 to 0x7FFF in the slave EEPROM as that is where the ISN is stored. Is that correct?

2. If 1. is true, will this impact the AIF or will I have to re-flash any data to the DME after I clear this portion of memory?

3. To define 'clear' - should I write 0x00 or 0xFF to the aforementioned area of ROM?

Thanks guys!
1) Yes thats correct, but you can keep the data around 0x5D00

2) No the AIF data is in the Primary eeprom not the slave so it won't effect it, you can however edit the AIF data if you wish, mine looks like it's only ever been flashed once.

3) You should fill the space with FF's, but don't forget to change 0x4800 after from all FF FF's to show 00 00 at the start (this is the flash counter area).


All that said, you could try just changing what is shown in red in the below picture, as everything else in that space (0x3FE4 to 0x7FFF) shows as either flash counter, manufacturer data or empty anyway (I have not tried just changing these bits though, so there could be more "hidden" data).


Last edited by cossie1; Thu, Jan-14-2016 at 02:29:27 PM.
Jump to top cossie1 is offline   Reply With Quote
Old Thu, Jan-14-2016, 01:12:23 PM   #3
ac427
Registered User
 
Join Date: Jun 2008
Posts: 465
Reputation: 0 ac427 is on a distinguished road
Location: London

United Kingdom




Default Re: MSS54HP EWS Virginization via BDM

Quote:
Originally Posted by cossie1 View Post
1) Yes thats correct, but you can keep the data around 0x5D00

2) If you clear the data from 0x3FE4 to 0x7FFF then you will clear the AIF anyway, so you would need to re-write this area after with Tool32 or reflash the dme with WinFKP I believe. I just deleted everything from the AIF area except the 1st entry, and entered the correct Vin for my car and it has been happy with that.

3) You should fill the space with FF's, but don't forget to change 0x4800 after from all FF FF's to show 00 00 at the start (this is the flash counter area).


All that said, you could try just changing what is shown in red in the below picture, as everything else in that space (0x3FE4 to 0x7FFF) shows as either flash counter, AIF or empty anyway (I have not tried just changing these bits though, so there could be more "hidden" data).


Hi Cossie, just so i get it. Will overwriting FF in the locations you have shown virginise the DME without the need to wipe the 0x3FE4 to 0x7FFF area ?

So would it be possible to write the VIN in, via a hex edit and then BDM flash, so you end up with a virgin DME but with a VIN?

What location is the VIN at ?
Jump to top ac427 is offline   Reply With Quote
Old Thu, Jan-14-2016, 01:19:37 PM   #4
cossie1
Registered User
 
Join Date: Dec 2013
Posts: 436
Reputation: 0 cossie1 is on a distinguished road

United Kingdom




Default Re: MSS54HP EWS Virginization via BDM

Quote:
Originally Posted by ac427 View Post
Hi Cossie, just so i get it. Will overwriting FF in the locations you have shown virginise the DME without the need to wipe the 0x3FE4 to 0x7FFF area ?

So would it be possible to write the VIN in, via a hex edit and then BDM flash, so you end up with a virgin DME but with a VIN?

What location is the VIN at ?
This is what I am thinking, but have not tested myself yet.

But every full bin i've looked at, has data written where those 6 FF's are located, and they are the only thing changed if you clear all data from 0x3FE4 to 0x7FFF except for the flash counter, manufacturer data and Vin data.

EDIT: Obviously in the above picture, I have just taken the screengrab from a full bin, before I split it into the master and slave, hence the address shown.

Last edited by cossie1; Thu, Jan-14-2016 at 01:51:58 PM.
Jump to top cossie1 is offline   Reply With Quote
Old Thu, Jan-14-2016, 01:51:02 PM   #5
cossie1
Registered User
 
Join Date: Dec 2013
Posts: 436
Reputation: 0 cossie1 is on a distinguished road

United Kingdom




Default Re: MSS54HP EWS Virginization via BDM

Quote:
Originally Posted by ac427 View Post
Hi Cossie, just so i get it. Will overwriting FF in the locations you have shown virginise the DME without the need to wipe the 0x3FE4 to 0x7FFF area ?

So would it be possible to write the VIN in, via a hex edit and then BDM flash, so you end up with a virgin DME but with a VIN?

What location is the VIN at ?
Sorry previous info was incorrect (I've updated my post) I was doing it from memory. AIF is in primary eeprom not the slave. The info around 0x5D00 in the slave is manufacturing data I think not the AIF.

Vin is in the primary eeprom at around 0x5D50 iirc and the vin is in there and could be repeated depending on how many updates your DME has had.

Last edited by cossie1; Thu, Jan-14-2016 at 02:32:00 PM.
Jump to top cossie1 is offline   Reply With Quote
Old Thu, Jan-14-2016, 04:54:37 PM   #6
terraphantm
Moderator
 
Join Date: Dec 2010
Posts: 11,356
In the garage:
Reputation: 11 terraphantm is on a distinguished road
Location: Philadelphia

United States




Default Re: MSS54HP EWS Virginization via BDM

Quote:
Originally Posted by cossie1 View Post
1) Yes thats correct, but you can keep the data around 0x5D00

2) No the AIF data is in the Primary eeprom not the slave so it won't effect it, you can however edit the AIF data if you wish, mine looks like it's only ever been flashed once.

3) You should fill the space with FF's, but don't forget to change 0x4800 after from all FF FF's to show 00 00 at the start (this is the flash counter area).


All that said, you could try just changing what is shown in red in the below picture, as everything else in that space (0x3FE4 to 0x7FFF) shows as either flash counter, manufacturer data or empty anyway (I have not tried just changing these bits though, so there could be more "hidden" data).

If you don't clear 0x3FE4 -> 0x3FE7, you won't be able to resync EWS. Those bytes show up as FF BMWFlash read, but they are populated in the BDM read.
__________________
Jump to top terraphantm is offline   Reply With Quote
Old Thu, Jan-14-2016, 07:05:57 PM   #7
cossie1
Registered User
 
Join Date: Dec 2013
Posts: 436
Reputation: 0 cossie1 is on a distinguished road

United Kingdom




Default Re: MSS54HP EWS Virginization via BDM

Quote:
Originally Posted by terraphantm View Post
If you don't clear 0x3FE4 -> 0x3FE7, you won't be able to resync EWS. Those bytes show up as FF BMWFlash read, but they are populated in the BDM read.
0x3FE4 -> 0x3FE7 ??
Jump to top cossie1 is offline   Reply With Quote
Old Thu, Jan-14-2016, 07:33:33 PM   #8
terraphantm
Moderator
 
Join Date: Dec 2010
Posts: 11,356
In the garage:
Reputation: 11 terraphantm is on a distinguished road
Location: Philadelphia

United States




Default Re: MSS54HP EWS Virginization via BDM

Quote:
Originally Posted by cossie1 View Post
0x3FE4 -> 0x3FE7 ??
Actually I meant 3fe9. 6 bytes (2 repeated 3 times)
__________________
Jump to top terraphantm is offline   Reply With Quote
Old Thu, Jan-14-2016, 07:34:04 PM   #9
terraphantm
Moderator
 
Join Date: Dec 2010
Posts: 11,356
In the garage:
Reputation: 11 terraphantm is on a distinguished road
Location: Philadelphia

United States




Default Re: MSS54HP EWS Virginization via BDM

Quote:
Originally Posted by cossie1 View Post
0x3FE4 -> 0x3FE7 ??
Actually I meant 3fe9. 6 bytes (2 bytes repeated 3 times)
__________________
Jump to top terraphantm is offline   Reply With Quote
Old Thu, Jan-14-2016, 07:45:02 PM   #10
cossie1
Registered User
 
Join Date: Dec 2013
Posts: 436
Reputation: 0 cossie1 is on a distinguished road

United Kingdom




Default Re: MSS54HP EWS Virginization via BDM

Quote:
Originally Posted by terraphantm View Post
Actually I meant 3fe9. 6 bytes (2 repeated 3 times)
I did go an look and noticed there was some data repeated between 0x3FE4 and 0x3FE9, hence me quoting for clarification.

So is it just that area that needs to be cleared now for the EWS to sync, or does the rest of it still need to be cleared too ?
Jump to top cossie1 is offline   Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump



All times are GMT. The time now is 03:07:37 PM.


Powered by vBulletin® Version 3.8.6
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.
M3Forum.com and M3forum.net is in no way sponsored, endorsed or affiliated by or with BMW NA / BMW AG or any of it's subsidiaries or vendors.
BMW and M3 (E90 M3 | E92 M3 | E93 M3 | E46 M3 | E36 M3 | E30 M3) are registered trademarks of BMW AG.
M3Forum Terms of Service
Copyright 1999-2017 M3Forum.com
Discussing Comprehensive MSS50 DME information (Euro E36 M3 S50B32 321 PS) in the Coding and Tuning Forum - Discuss all avenues of coding and tuning here! at BMW M3 Forum.com (E30 M3 | E36 M3 | E46 M3 | E92 M3 | F80/X)