Pages: 1 ... 51 52 [53] 54
Author Topic: ME7 EEPROM programmer  (Read 412011 times)
B5Quattrolife
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 13


« Reply #780 on: January 14, 2019, 12:00:51 PM »

C:\Users\Tyler Ward>"C:\Users\Tyler Ward\Desktop\ME7 XDF-BIN files\TunerPro File
s\Bins\me7_95040.exe" --bootmode -r -p 2 95040.bin
Ver: 1.31
Com Port: 2
Baud Rate: 10400
Opening COM2 ... OK
Starting Boot_mode ... uC identification response = 0xC5 (C167 derivatives) ...
OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... FAIL. (error=0x01)
Closing COM2

Also this, any help is greatly appreciated, ECU is in boot mode and i dont get past confirming a com port in --OBD mode
Logged
bamofo
Full Member
***

Karma: +0/-2
Offline Offline

Posts: 52


« Reply #781 on: January 23, 2019, 02:03:25 PM »

C:\Users\Tyler Ward>"C:\Users\Tyler Ward\Desktop\ME7 XDF-BIN files\TunerPro File
s\Bins\me7_95040.exe" --bootmode -r -p 2 95040.bin
Ver: 1.31
Com Port: 2
Baud Rate: 10400
Opening COM2 ... OK
Starting Boot_mode ... uC identification response = 0xC5 (C167 derivatives) ...
OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... FAIL. (error=0x01)
Closing COM2

Also this, any help is greatly appreciated, ECU is in boot mode and i dont get past confirming a com port in --OBD mode

Ive been wrong before... but i believe with --bootmode you have to have the memory type after it so it knows what to do.. for instance on my b6s4 i have to do

--bootmode 95P08

Try that except with what you are using which is 95040


so in your case

me7_95040.exe --bootmode 95040 -r -p 2 -b 57600 95040.bin
« Last Edit: January 23, 2019, 02:05:33 PM by bamofo » Logged
rysiektr
Newbie
*

Karma: +0/-3
Offline Offline

Posts: 17


« Reply #782 on: January 30, 2019, 04:08:24 AM »

Hi everyone,

Have you tested that ME7_95040 tool for ME 7.1.1 with 95160?
In attach is photo of that ECU.
I read that 95160 memory, do immo off with that tool, immo is off, checksum is ok. On VCDS in Adaptation channel no. 91 is value 1 so it means immo is off, but I have 2 problems:
1. I can't read any DCT's via VAG-COM
2. I can't read software from that ECU via MPPS - I have error "ECU is prottected" or some simmilar comunicate I can't remmember.

I can't connect that ECU to car for a tests if immo is off.

Have you got similar problems? How to solve it?

Regards 
Logged
dirtnasty
Full Member
***

Karma: +7/-11
Offline Offline

Posts: 169


« Reply #783 on: February 10, 2019, 09:49:43 PM »

Hi everyone,

Have you tested that ME7_95040 tool for ME 7.1.1 with 95160?
In attach is photo of that ECU.
I read that 95160 memory, do immo off with that tool, immo is off, checksum is ok. On VCDS in Adaptation channel no. 91 is value 1 so it means immo is off, but I have 2 problems:
1. I can't read any DCT's via VAG-COM
2. I can't read software from that ECU via MPPS - I have error "ECU is prottected" or some simmilar comunicate I can't remmember.

I can't connect that ECU to car for a tests if immo is off.

Have you got similar problems? How to solve it?

Regards 
a picture of the label doesn't help much. open the ecu and look for the immo chip that has the memory numbers on it so you are 1000% sure what memory flag to use in the me7 tool


if immo is off then the only issue you should have is trying to program new keys


if you are trying to read the ecu flash and it says request upload blocked then it is tuned with a locked file ie. giac apr eurodyne etc..


it would help also if you posted the immo file you are trying to fix
i'll try my best to help you
« Last Edit: February 10, 2019, 09:58:55 PM by dirtnasty » Logged
rysiektr
Newbie
*

Karma: +0/-3
Offline Offline

Posts: 17


« Reply #784 on: February 11, 2019, 04:29:58 AM »

a picture of the label doesn't help much. open the ecu and look for the immo chip that has the memory numbers on it so you are 1000% sure what memory flag to use in the me7 tool


if immo is off then the only issue you should have is trying to program new keys


if you are trying to read the ecu flash and it says request upload blocked then it is tuned with a locked file ie. giac apr eurodyne etc..


it would help also if you posted the immo file you are trying to fix
i'll try my best to help you

Hi, Thanks for your answer.
I'm really sure that the memory of the ECU is 95160 becose first I open ECU and then read the memory.
I no needed to program new key, that ECU and R32 engine will be install in VW golf mk2. I need to do only immo off and I do this via 95040tool but if immo is not off then you can't read and write flash from ECU.
On VCDS in Adaptation channel no. 91 is value 1 so it means immo is off but I still can't read and write software via MPPS.
I think that the ECU have OEM software, but if not it is possible to unlock that ECU?
Logged
BlackT
Sr. Member
****

Karma: +9/-3
Offline Offline

Posts: 328



« Reply #785 on: February 18, 2019, 12:36:29 PM »

Here I will try to explain how to find CS pin. It is not that hard but for someone who is first time with electronics,can be real struggle...

When you get this error:

Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... FAIL. (error=0x70C01)
Closing COM2

You will need to find CS pin by yourself.

First locate the EEPROM, On 2.7 ECU is here

On 1.8T ECU here


Then follow the electric trace from EEPROM to the main CPU
https://www.youtube.com/watch?v=rSfgH9PO3N8&feature=youtu.be

In my case that is pin 92 or  P4.7


So again in CMD when I set CS P4.7 i am able to write EEPROM


ME7EEPROM.exe --bootmode 95040 --CSpin P4.7 -wp2 2.7Mimmooff_sum.bin
ME7_EEPROM v1.40
COM: 2, Baud Rate: 10400
Memory type: 95040, size: 512
Chip Select pin: P4.7
Opening COM2 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Writing EEPROM ................................ OK
Verifying EEPROM write ... FAIL. (error=0x70101)
Closing COM2

And that is all, i hope i will help someone Smiley Smiley
Logged
adrianglasgow
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7


« Reply #786 on: February 22, 2019, 12:20:16 PM »

Hi guys Im using this tool for the first time and have a weird problem. The whole process goes as it should. It says:
Reading EEPROM ... OK
File saved
Closing COM1
.........but I cant find the file anywhere on my computer. Am I missing something obvious?
Logged
dal
Full Member
***

Karma: +1/-2
Offline Offline

Posts: 85



WWW
« Reply #787 on: February 22, 2019, 12:57:04 PM »

Are you specifying the output file in the command?
Logged

Audi A3 8L
1984cc stroker - E100 - ME7 wideband converted - 400whp target
Instagram: @a3stroker
adrianglasgow
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7


« Reply #788 on: February 22, 2019, 01:25:43 PM »

I think so.
Here are the commands I use.
C:\a\ME7 --bootmode 95040 -p 1 -r 95040.bin

I can view the content of the eeprom by using the --screen command so the comunication is there but I cant find the saved file.
Logged
BlackT
Sr. Member
****

Karma: +9/-3
Offline Offline

Posts: 328



« Reply #789 on: February 22, 2019, 02:53:16 PM »

If you are using Win 7, file will save in
C:\users\(your_user_account _name)\
Xp documents and settings\users\(your_user_account _name)\
Logged
adrianglasgow
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7


« Reply #790 on: February 23, 2019, 02:53:53 AM »

Thanks guys. Its the win XP I use.
I noticed on the back of the board that it has eeprom SP08C3 soldered in instead of the 95040. I know that this ecu has been previously messed with by Revo.
The programer still accepts 95040 commands to talk to it but even though it says that it saves the file it doesnt actually do it. At least thats how I understand it. I also tried writing another file to the eeprom and even though the writing is succesful it failes to verify the eeprom afterwards and when I check the content with - - screen commands the file is unchanged. I dont know why Revo would do it other than some sort of protection. I also noticed that the content of the eeprom already has the immo removed. I was using this ecu as I had it lying around and wanted to learn to use the me7eeprom tool so Ill get another ecu to play with and I guess it should work then.
Logged
Maxohio
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 64


« Reply #791 on: April 08, 2019, 11:18:36 PM »

Here I will try to explain how to find CS pin. It is not that hard but for someone who is first time with electronics,can be real struggle...

When you get this error:

Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... FAIL. (error=0x70C01)
Closing COM2

You will need to find CS pin by yourself.

First locate the EEPROM, On 2.7 ECU is here

On 1.8T ECU here


Then follow the electric trace from EEPROM to the main CPU
https://www.youtube.com/watch?v=rSfgH9PO3N8&feature=youtu.be

In my case that is pin 92 or  P4.7


So again in CMD when I set CS P4.7 i am able to write EEPROM


ME7EEPROM.exe --bootmode 95040 --CSpin P4.7 -wp2 2.7Mimmooff_sum.bin
ME7_EEPROM v1.40
COM: 2, Baud Rate: 10400
Memory type: 95040, size: 512
Chip Select pin: P4.7
Opening COM2 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Writing EEPROM ................................ OK
Verifying EEPROM write ... FAIL. (error=0x70101)
Closing COM2

And that is all, i hope i will help someone Smiley Smiley

Thanks for that!, What happends if written to wrong pin before?
Will that brick ECU, of can i still write to the right pin?
Logged
snowzach
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 3


« Reply #792 on: April 25, 2019, 07:05:04 PM »

Was the source ever posted for this program? I couldn't find it. I busted my eeprom and put an empty one in. The write protect is turned on and I wanted to mod the program to optionally turn it off. Just curious.
Logged
nyet
Administrator
Hero Member
*****

Karma: +429/-53
Offline Offline

Posts: 9711


WWW
« Reply #793 on: April 25, 2019, 07:06:40 PM »

Was the source ever posted for this program? I couldn't find it. I busted my eeprom and put an empty one in. The write protect is turned on and I wanted to mod the program to optionally turn it off. Just curious.

Sadly, no, and I can't seem to contact the author.
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
Steve Bassen
Newbie
*

Karma: +2/-0
Offline Offline

Posts: 19


« Reply #794 on: August 10, 2019, 07:37:24 PM »

Has anyone been able to read the eeprom of a Touareg ecu (especially a 4D0 907 560 DB)?  I've used both 1.31 and 1.4 and can't get it to read, either via OBD or bootmode.  I've done this tons of time on 518 and 551 ECU's, previously...  Soon as it gets to Starting Boot_mode it errs with 0x09 and then hangs the command prompt, requiring a reboot.
Logged
Pages: 1 ... 51 52 [53] 54
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.027 seconds with 18 queries. (Pretty URLs adds 0s, 0q)