Pages: 1 ... 54 55 [56] 57 58 ... 63
Author Topic: ME7 EEPROM programmer  (Read 843474 times)
doublerwest
Full Member
***

Karma: +5/-4
Offline Offline

Posts: 178



« Reply #825 on: August 06, 2020, 05:58:33 PM »

ok ladies and gents i have come a very long way in my journey to learn all this ME7 ECU coding. Its incredible what ArgDubs tool can do I am stuck trying to get an SKC from a replacement ECU. I have my current SKC code and just need to get the code from the new one. I have the ECU connected to vehicle and Laptop is connected to OBD. I have read all info from my old ECU.
With the new ECU in vehicle and trying to read it the same way i did with the old ECU i cannot get in
No ECU response. (error=0x20F07)
boot mode bro ...boot mode
Logged

W357
Bumequipment
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 8


« Reply #826 on: August 06, 2020, 06:02:51 PM »

boot mode bro ...boot mode
I still don't know what boot mode is although I have managed to get in and get SKCs and swap ECUs already. Next question can you swap 7.1.1 Software to 7.5 hardware? Will it work if I write my VR6 to my 2.0 ECU?

Sent from my SM-N960U using Tapatalk

Logged
doublerwest
Full Member
***

Karma: +5/-4
Offline Offline

Posts: 178



« Reply #827 on: August 06, 2020, 06:26:16 PM »

I still don't know what boot mode is although I have managed to get in and get SKCs and swap ECUs already. Next question can you swap 7.1.1 Software to 7.5 hardware? Will it work if I write my VR6 to my 2.0 ECU?

Sent from my SM-N960U using Tapatalk


not sure about the immo dumps from me 7.1.1 to 7.5 but you can do immo off and run the ecu with a bin file that is identical engine platforms what you have as i have done a 7.1.1 to me 7.5 ecu swap from  passat 1.8t into audi a4 1.8t different kwp but it is  much more advanced ecu so if its identical hardware mechanically it should be a drop in with immo off mods but boot mode is a pin to ground on me 7 ecu you gotta hit to write with that program if i knew where the write up was id send you the link someone else may have it if i find it ill send it to you. if its not similar ecu to what you had im pretty sure you will brick the ecu then you will have to learn boot mode 2.0 is inline 4 yes? way different controller but its out of my knowledge base
« Last Edit: August 06, 2020, 06:36:15 PM by doublerwest » Logged

W357
doublerwest
Full Member
***

Karma: +5/-4
Offline Offline

Posts: 178



« Reply #828 on: August 06, 2020, 06:35:13 PM »

if you google boot mode for flashin me7.5 ecu itll pop up on how to do it but you have to do boot mode as if you here lighting a furnace you do the boot mode pin hold and power up for a 6 second hold and then hit write after you let up on the ground pin after 6 seconds itll write with eeprom programmer if you commanded it to write in boot mode with com port the cable is on and what not you may need to read some more before you try this works good!! but get a ecu that is identical to what engine you have your gunna be working youself in circles diffrent ecu have diffrent controllers like 1.8 prolly wont work in a v6 unless its identical hardware but still its hardwired to 4 cylinder
« Last Edit: August 06, 2020, 06:41:38 PM by doublerwest » Logged

W357
doublerwest
Full Member
***

Karma: +5/-4
Offline Offline

Posts: 178



« Reply #829 on: August 06, 2020, 06:47:21 PM »

helping you and doing it for you are two totally different things

you are just lazy, nothing more
ya there are tons of write ups on here to do it to comand line bro learn that command line jeez i have spent hours learning this programmer fiqured it out he should be able to fiqure it out!!!!! if he got that far to pull the file he is half way there!!!
Logged

W357
nhatquang88
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 1


« Reply #830 on: August 22, 2020, 11:05:20 AM »

I have a Bentley continental which is the same as Audi A8 or VW phaeton,,
I want to read this eeprom via OBD but I wonder what chip it will have or it will auto detect?
95040 or 95160 or ...?
Thank you alot
Logged
bugmeister
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 1


« Reply #831 on: September 05, 2020, 03:02:45 AM »

Hi,

Today I read and wrote my primary ECU successfully in boot mode, however my secondary ECU throws the following error attempting to read:

ME7_EEPROM v1.40
COM: 4, Baud Rate: 10400
Memory type: 95040, size: 512
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... FAIL. (error=0x20D07)
Closing COM4

Any ideas or suggestions?  I tried different baud rate to no avail Sad

Cheers
Peter
Logged
jockie22
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 1


« Reply #832 on: September 15, 2020, 08:59:07 AM »

Hi,

While trying to use this program with an ECU from a 2003 Golf Mk4 we were faced with this error:

ME7EEPROM.exe --bootmode 95040 --CSpin P4.7 -rp4 -b 9600 old.bin
ME7_EEPROM v1.40
COM: 4, Baud Rate: 9600
Memory Type: 95040, size: 512
Chip Select pin: P4.7
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... FAIL. <error=0x40101>
Closing COM4

Has someone ever encountered this problem before ? We would really appreciate some help.

Thanks.
Logged
bamofo
Sr. Member
****

Karma: +34/-3
Offline Offline

Posts: 420


« Reply #833 on: September 16, 2020, 10:04:20 AM »

Hi,

While trying to use this program with an ECU from a 2003 Golf Mk4 we were faced with this error:

ME7EEPROM.exe --bootmode 95040 --CSpin P4.7 -rp4 -b 9600 old.bin
ME7_EEPROM v1.40
COM: 4, Baud Rate: 9600
Memory Type: 95040, size: 512
Chip Select pin: P4.7
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... FAIL. <error=0x40101>
Closing COM4

Has someone ever encountered this problem before ? We would really appreciate some help.

Thanks.

have you tried reading it not in boot mode to see what it selects on its own? or do you use this tool all the time and randomly your facing this issue?
Logged
jjameson96
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 1


« Reply #834 on: September 19, 2020, 01:49:37 PM »

Hello, first of all excellent bit of software.
However it hasn't been so sucessful for me (yet) so i started off and after a few failed atempts i manged to read the eeprom on the bench with a generic kkl cable in boot mode, then had every error known trying to write or read again, eventually it suddenly let me read again and write so i uploaded the immo off file and all went ok, although the ecu now appears to do minimal when connected to the car and vcds won't find it either.

here's a few sections from the command prompt, cheers

Quote
C:\Users\jorda>C:\Users\jorda\Downloads\ME7EEPROM.exe --bootmode 95040 --CSpin P4.7 -b 9600 -r -p 2 95040.bin
ME7_EEPROM v1.40
COM: 2, Baud Rate: 9600
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
Reading EEPROM ... OK
File saved
Closing COM2

C:\Users\jorda>C:\Users\jorda\Downloads\ME7EEPROM.exe --bootmode 95040 --CSpin P4.7 -b 9600 -w -p 2 95040.bin
ME7_EEPROM v1.40
COM: 2, Baud Rate: 9600
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
Closing COM2

This is all it gives me now since uploading the data

Quote
C:\Users\jorda>C:\Users\jorda\Downloads\ME7EEPROM.exe --bootmode 95040 --CSpin P4.7 -b 9600 -w -p 2 95040.bin
ME7_EEPROM v1.40
COM: 2, Baud Rate: 9600
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 ... FAIL. (error=0x20F07)
Closing COM2


And here's some of the other random errors, i could try it 3 times in a row and get 3 different errors



Quote
C:\Users\jorda>C:\Users\jorda\Downloads\ME7EEPROM.exe --bootmode 95040 --CSpin P4.7 -r -p 2 95040.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 ... FAIL. (error=0x40B01)
Closing COM2

C:\Users\jorda>C:\Users\jorda\Downloads\me7_95040_v1.31\me7_95040.exe --bootmode -b 9600 -r -p 2 95040.bin
Ver: 1.31
Com Port: 2
Baud Rate: 9600
Opening COM2 ... OK
Starting Boot_mode ... uC identification response = 0xC5 (C167 derivatives) ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... FAIL. (error=0x01)
Closing COM2

C:\Users\jorda>C:\Users\jorda\Downloads\me7_95040_v1.31\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 ... ... OK
Sending EEPROM driver ... FAIL. (error=0x01)
Closing COM2


Thanks, not really sure where to go from here as i've got a long list of things i've tried and the errors just chop and change randomly
Logged
TurboMMJ
Newbie
*

Karma: +0/-4
Offline Offline

Posts: 22


« Reply #835 on: October 02, 2020, 07:52:16 AM »

hi all ,

absolute monster tool for us hobylists thanks to all involved in it !

unfortunately still cant get success , tried 2ea me7.5 ecus both TT 95040 eeprom , trying only in BOOT mode on the bench(kitchen table)
using KKL 409.1 china cable set to COM 8 bits rate 9600
found many errors inbetween many tries , found out wait for capacitors to go down is less errorable but cant read fully .

here is some examples :

D:\me7eprom>ME7EEPROM  --bootmode 95040 -r -p 8 -b 9600  95040.bin
ME7_EEPROM v1.40
COM: 8, Baud Rate: 9600
Memory type: 95040, size: 512
Opening COM8 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... FAIL. (error=0x40901)
Closing COM8



D:\me7eprom>ME7EEPROM  --bootmode 95040 -r -p 8 -b 9600  95040.bin
ME7_EEPROM v1.40
COM: 8, Baud Rate: 9600
Memory type: 95040, size: 512
Opening COM8 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... FAIL. (error=0x40701)
Closing COM8






any help please
cheers
Logged
R32Dude
Full Member
***

Karma: +45/-10
Offline Offline

Posts: 246



« Reply #836 on: October 28, 2020, 12:28:37 AM »

Although the ST10 as used in the ME7.1.1   is not supported, a simple edit to the V1.4 ME7eeprom.exe allowed me to read and write to my ecu with the 95160 eeprom from a 2008 R32 Golf. I simply edit the exe as shown below and run one of the two commands to read or write. The port number will depend on your PC. I used a HEX-CAN cable with VCP drivers installed.  I had first removed the eeprom and read it with a cheap reader. After soldering back, and booting  back to boot mode I read it with the modified program. It matched the original perfectly. Next I rebooted and wrote  to the EEPROM a file full of 99 hexes. It wrote without problems, but gave an error when it tried to verify it back.  After rebooting the ecu again, I read it back using the modified program and the files matched perfectly -all 99 hex! So it does write. Then I wrote to it an immo off version of the original and once again I got verification error, but in reality it actuallyit did the job. Phew Cry Cry  Use at your own risk. It worked for me but may not for you.

The mod is to  change the 84 to 85

commands used:
me7eeprommod   -b9600 -p 3 --bootmode 95160 --CSpin P6.3 -w immo.bin
 me7eeprommod   -b9600 -p 3 --bootmode 95160 --CSpin P6.3 -r readout.bin


« Last Edit: October 28, 2020, 12:32:41 AM by OZZIE1 » Logged
Markus1982
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 2


« Reply #837 on: October 30, 2020, 09:39:14 AM »

Hi,
I Have a Problem to read my EEPROM from an AUDI S8 MY2000

Can anybody help me?
Logged
stuydub
Full Member
***

Karma: +24/-12
Offline Offline

Posts: 227


« Reply #838 on: October 31, 2020, 05:32:58 AM »

After every attempt of bootmode fail (MONITER) error u need to turn off rig and re bootmode ecu..and in stead of using the command lines use the Me7GUI version if u struggling..
Logged
mdccode5150
Full Member
***

Karma: +11/-4
Offline Offline

Posts: 122


« Reply #839 on: November 04, 2020, 10:10:08 PM »

OK read 50+ pages of noobs, com port, CMD and cable problems...I only found a couple of similar problems to mine. I did learn somethings. It worked but the file was all FF's, and the File ended up here (C:\Users\Michael\AppData\Local\VirtualStore)

So here is the two problems 1) I have a Porsche ME7.1.1 (I think maybe a ME7.2?) and it has a 35P08 3 EEPROM and here is what I did:

C:\>ME7EEPROM -p 4 --bootmode 95P08 --CSpin P4.7 -r 95P08.bin
ME7_EEPROM v1.40
COM: 4, Baud Rate: 10400
Memory type: 95P08, size: 1024
Chip Select pin: P4.7
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xD5 ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Reading IDCHIP ... 0x0C43: C167CS ... OK
Initializing registers ... OK
Sending EEPROM driver ... OK
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00FF
Reading EEPROM ... OK
File saved
Closing COM4

2) and the second issue

The file ended up here:

C:\Users\Michael\AppData\Local\VirtualStore


I think I used the wrong CSpin!?
Logged
Pages: 1 ... 54 55 [56] 57 58 ... 63
  Print  
 
Jump to:  

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