NefMoto

Technical => Reverse Engineering => Topic started by: vwnut8392 on March 28, 2016, 03:35:17 PM



Title: VW 2.5 I5 ME7 different than other ME7 ECU's?
Post by: vwnut8392 on March 28, 2016, 03:35:17 PM
i was looking at the BIN file from my 2006 jetta 2.5 parts/swap car and i decided to give the LC/NLS patcher a go for fun to see if it would do it. when i tried basically the patch said WTF is this? lol. anyone else ever notice this or is it just me?


Title: Re: VW 2.5 I5 ME7 different than other ME7 ECU's?
Post by: ddillenger on March 28, 2016, 06:03:27 PM
Very different. Depending on the year, it's ST10. Most code IIRC is stored in the MPC.


Title: Re: VW 2.5 I5 ME7 different than other ME7 ECU's?
Post by: vwnut8392 on April 02, 2016, 12:59:45 PM
Very different. Depending on the year, it's ST10. Most code IIRC is stored in the MPC.

Are there non ST10 ECU's? like from a really early car? VW is notorious for putting left over's from previous models in the first run of the new models. i have 70K906032AN from 6-2006 build automatic jetta.


Title: Re: VW 2.5 I5 ME7 different than other ME7 ECU's?
Post by: ddillenger on April 02, 2016, 03:46:33 PM
Yes. The single letter, MAF cars have the traditional configuration.



Title: Re: VW 2.5 I5 ME7 different than other ME7 ECU's?
Post by: vwnut8392 on April 06, 2016, 09:19:42 PM
Yes. The single letter, MAF cars have the traditional configuration.



Whats weird is my car has both MAF and MAP sensor. the ending prefix is AN for the the ECU #. i've seen pictures of the inside of the ST10 ECU and it did say ST10 right on the processor but the thing is mine doesnt. mine says infineon-B00119-1037367435-copyright BOSCH-siemens 97. maybe i have some weird crossover ECU or something. i also wonder if i could load a single prefix file into this ECU to run on the more common file?


Title: Re: VW 2.5 I5 ME7 different than other ME7 ECU's?
Post by: k0mpresd on April 06, 2016, 10:19:06 PM
c167 ecus have the data area @ 0x10000. st10 have the data area at the bottom of the file. pretty easy to distuingish.
2006 is c167. st10 started in some 07 and above.

code is not in st10. code is still stored in 800bb flash. there is a specific mcu file matching the flash version though in the st10 ecus.
*worth noting the sgo update for st10 ecus contain both flash and matching st10 update.

032an is c167 btw.

this is a matching st10 file set (flash, mcu, e2p) for 3.2 ecu if you'd like to see the different files: http://nefariousmotorsports.com/forum/index.php?topic=9025.0title=


Title: Re: VW 2.5 I5 ME7 different than other ME7 ECU's?
Post by: prj on April 07, 2016, 01:19:30 AM
code is not in st10.

Are you sure?  ::)


Title: Re: VW 2.5 I5 ME7 different than other ME7 ECU's?
Post by: eliotroyano on April 07, 2016, 05:49:53 AM
I know that many Fiat and VW South American vehicle ECUs are ST10 Microprocessor based and are complicated to work with. I also know that exist a ST10Flasher interface specific to work with this ECUs. About Flash-MCU-E2P data relation, that could explains why these type of ECUs are so tricky to immo off and some models inclusive to modify or tune. Well it is only my little experience.


Title: Re: VW 2.5 I5 ME7 different than other ME7 ECU's?
Post by: k0mpresd on April 07, 2016, 06:16:28 AM
Are you sure?  ::)

Most code IIRC is stored in the MPC.

is what i was clarifying.
there is code in st10 cpu, as i wrote there is an mcu file. but the maps are not in st10. to read/write tune, st10 is untouched.


Title: Re: VW 2.5 I5 ME7 different than other ME7 ECU's?
Post by: ddillenger on April 07, 2016, 03:31:51 PM
is what i was clarifying.
there is code in st10 cpu, as i wrote there is an mcu file. but the maps are not in st10. to read/write tune, st10 is untouched.

I wasn't implying that to "tune" would require modding the ST10, however any code changes would.


Title: Re: VW 2.5 I5 ME7 different than other ME7 ECU's?
Post by: k0mpresd on April 07, 2016, 04:02:25 PM
I wasn't implying that to "tune" would require modding the ST10, however any code changes would.

just making sure everyone was on the same page. didn't want them to think st10 was part of if.  :)