Pages: 1 ... 58 59 [60] 61 62 63
Author Topic: ME7 EEPROM programmer  (Read 922966 times)
EuroXs4
Full Member
***

Karma: +15/-31
Offline Offline

Posts: 209


« Reply #885 on: December 02, 2021, 08:52:15 PM »

Is it possible to use this tool with 2002 porsche 996??
Logged
prj
Hero Member
*****

Karma: +1072/-481
Offline Offline

Posts: 6037


« Reply #886 on: December 03, 2021, 10:24:50 AM »

Did you try?

It doesn't matter what the ECU is, it loads a bootstrap loader and you have to specify the pin the EEPROM is connected to (if it can't detect automatically).
It will work even with a non-Bosch ECU as long as the micro is a C166/C167.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
bazgreener
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 10


« Reply #887 on: December 18, 2021, 11:12:12 AM »

Hi all,
   moved along a little further with the ECU but now hit another stumbling block   Roll Eyes
Any ideas why i am seeing this error? 

Thanks

C:\Users\Bazza>ME7_95040 --bootmode -r -p 4 -b 9600 95040.bin
Ver: 1.31
Com Port: 4
Baud Rate: 9600
Opening COM4 ... 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 COM4
Logged
_nameless
Hero Member
*****

Karma: +342/-466
Offline Offline

Posts: 2802



« Reply #888 on: December 18, 2021, 12:07:13 PM »

Hi all,
   moved along a little further with the ECU but now hit another stumbling block   Roll Eyes
Any ideas why i am seeing this error? 

Thanks

C:\Users\Bazza>ME7_95040 --bootmode -r -p 4 -b 9600 95040.bin
Ver: 1.31
Com Port: 4
Baud Rate: 9600
Opening COM4 ... 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 COM4
the answer is literally in the post directly above yours
Logged

Giving your mom a tuneup
bazgreener
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 10


« Reply #889 on: December 18, 2021, 12:38:17 PM »

the answer is literally in the post directly above yours
Grin How the hell did i not see that !
Next question, what pin is my eeprom connected to?
Logged
bazgreener
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 10


« Reply #890 on: December 26, 2021, 07:46:50 AM »

Can anyone advise how i input the EEPROM pin into the command prompt? I see from some previous posts on ME7_95040 that the pin is listed as P4.7 (i know this may not be the correct pin for my ecu) but how would i tell ME7_95040 to look for the pin? when -P is already used to identify the com port.

Thanks
Logged
BlackT
Hero Member
*****

Karma: +79/-40
Offline Offline

Posts: 1425



« Reply #891 on: January 11, 2022, 02:19:43 AM »

--CSpin P4.7 or P6.3 for ME7.1.1
Logged
pr0dukt
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 1


« Reply #892 on: February 26, 2022, 01:51:55 AM »

Hopefully someone is still around to answer this, but I'm having a hell of a time getting a good ECU dump from an OBDII read using any of the software I've gotten ahold of, this tool included. I have a dead/unreadable Magneti Cluster in a 2005 beetle, that pairs to an ME7.1.1 ECU w/ AM29F800BB layout. I Located a used cluster that I could use for a swapin. However being unable to access the old cluster, prevents me from pulling any of the data off it for cloning (unless I want to set up a bench and extract chip for r/w I suppose which I'm in no position to do atm), So I've been going at it from scratch trying to adapt this new cluster..
My main hurdle atm is just retrieving the SKC of the dead cluster from my ECU's EEPROM (this vehicle is on immo3), as it's my only real option for adapting and rekeying. I have a HEX-V2 rtech cable for VCDS, for adaption once pins are retrieved.. As far as the EEPROM retrieval, I've Tried both a ch340 KKL dumb cable, and a FT232RL K+Can 1.4 cable with no successful full reads. I've tried using vag tacho, eeprom programmer, k+can commander 1.4/2.5, and visualME7logger. With this tool (v1.4) showing the most promise. It reads for a while but then ends up erroring out before finishing the read.

I'm doing this with my voltage at roughly 13.6vdc while on a bat charger. I have not attempted a read in boot mode yet. I suppose that will be my next endeavor. I believe it's still the 24-pin on the flash chip to bootmode enable the ecu correct? once in boot mode, my chances of getting a full read via ODBII should significantly improve I imagine,. Though I thought it was possible to dump without needing to utilize bootmode, so I really didn't want to have to bother going that far. Though than again, I've read about various troubles getting eeprom from me7.1.1 on other forums so maybe I'm just going through the normal process of smashing one's head against the controller in every conceivable way before it gives me what I want..

Is there any other caveats that will make this process go smoother? I plan to just straight edit the EEPROM of the new(used) cluster to my present ECU's vin+immo+skc data via HxD or the like, and flashing it back to the cluster.. but until I get this shitty skc, I can't do jack to progress.

Any protips are much obliged.
« Last Edit: February 26, 2022, 02:13:35 AM by pr0dukt » Logged
sherpagoodness
Newbie
*

Karma: +1/-0
Offline Offline

Posts: 11


« Reply #893 on: February 26, 2022, 04:06:54 PM »

yea, you need boot mode. it may take a few tries to get it in boot mode, but don't give up Cheesy
Logged
JakeGT
Newbie
*

Karma: +0/-1
Offline Offline

Posts: 21


« Reply #894 on: March 28, 2022, 11:47:57 AM »

Hi I keep getting this error but can't figure out why can anyone help? I've successfully read before in the past ok.

ME3.1 thanks

C:\Users\satel>C:\Users\satel\Desktop\ECU\Nefmoto\ME7EEPROM_1.4.exe --bootmode 95080 -r -p3 --CSpin P4.7 2803.bin
ME7_EEPROM v1.40
COM: 3, Baud Rate: 10400
Memory type: 95080, size: 1024
Chip Select pin: P4.7
Opening COM3 ... OK
Starting Boot_mode ... uC ID response 0x00. Unknown ID. (error=0x40201)
Closing COM3
Logged
Groopan
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 31


« Reply #895 on: April 13, 2022, 06:48:58 AM »

Good day

Need some advice please , i have used these CLI apps with no problem in the past . i am currently going crazy trying to get them to run on win10 , win 7 , i even tried VM win7 and xp.

The CMD just opens in a new window and flashes and  closes , i manage to slow down my PC and confirm the CLI app is opening but it shuts off . i have tries veryting thing i could find online  oh how i can correct this but notting seems to work , new user accound , scf , admin , nothing works .

here is a video of what happens
https://youtu.be/QWWwTa-gzvE

Please advise how i can correct this and get the CLI to run

thank you again for your help
Logged
adam-
Hero Member
*****

Karma: +124/-33
Offline Offline

Posts: 2179


« Reply #896 on: April 13, 2022, 06:53:28 AM »

You're using CMD wrong.  CD to the path you need, then run it.
Logged
Groopan
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 31


« Reply #897 on: April 13, 2022, 07:00:30 AM »

You're using CMD wrong.  CD to the path you need, then run it.

Same thing happens  CMD opens another window the CLI flashes and shuts off . i have done this before with no issues for some strange reason no matter what computer i try it on its the same issue . i redownloaded the apps , i have use the current drictory for the exe file  but i am having the same issue
Logged
Geomeo
Full Member
***

Karma: +11/-6
Offline Offline

Posts: 152


« Reply #898 on: April 13, 2022, 11:02:56 AM »

I'm not sure how it is in Winodws 7, but in the search box type cmd then right click run as administrator.  When you reinstalled Windows did you do all of the windows updates?  Try running any dot exe from the cmd prompt and see what happens.
Logged
Groopan
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 31


« Reply #899 on: April 13, 2022, 04:05:36 PM »

I'm not sure how it is in Winodws 7, but in the search box type cmd then right click run as administrator.  When you reinstalled Windows did you do all of the windows updates?  Try running any dot exe from the cmd prompt and see what happens.

So 7 is updated 10 is in the process of being updated. Both run .exe apps from cmd . Just when I try to run these cli apps it just opens In a new cmd window and closes . Does the same on both 10 and 7 also I tried redownloading apps and same thing .
Logged
Pages: 1 ... 58 59 [60] 61 62 63
  Print  
 
Jump to:  

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