NefMoto > Technical > Cluster and Immobilizer (Moderator: ddillenger) > ME7 EEPROM programmer
Pages: 1 ... 62 63 [64]
« previous next »
Author Topic: ME7 EEPROM programmer  (Read 996620 times)
JeanAwt
Sr. Member
****

Karma: +11/-12
Offline Offline

Posts: 254
« Reply #945 on: December 28, 2024, 05:08:42 AM »
Quote from: joshw3794 on December 27, 2024, 11:41:26 AM
i am using blue kkl cable but its ch340 and keeps saying comunnication fail how do i fix???

Buy ft232rl
Logged
A4 B5 avant 1.8T 2000 NO QUATTRO
mRj
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 38
« Reply #946 on: January 06, 2025, 11:32:55 AM »
Quote from: ChameleonD on June 09, 2022, 02:53:26 PM
Could you please tell how do you solve this problem?

i have the same error, struggling to write it back.

i have read it fine.

This is the error on both 1.31 and 1.40 on me7.5 out of an Audit TT (BAM)
Happens on both win10 and xp

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
« Last Edit: January 06, 2025, 12:57:50 PM by mRj » Logged
mRj
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 38
« Reply #947 on: January 08, 2025, 01:50:47 AM »
Quote from: mRj on January 06, 2025, 11:32:55 AM
i have the same error, struggling to write it back.

i have read it fine.

This is the error on both 1.31 and 1.40 on me7.5 out of an Audit TT (BAM)
Happens on both win10 and xp

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


I have fixed this, using a red VAG.KKL cable (shown as serial port on device manager)
Also, only 1.31 worked, 1.40 failed to verify the Eeprom.
« Last Edit: January 11, 2025, 08:00:19 AM by mRj » Logged
Rick81
Full Member
***

Karma: +0/-11
Offline Offline

Posts: 118
« Reply #948 on: January 10, 2025, 07:58:55 PM »
I'm glad it worked out. I've also got the Vag kkl cable and carnt get the program to read. How long did you leave the boot pin on for. Or should I say what did you do
Logged
mRj
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 38
« Reply #949 on: January 11, 2025, 08:04:43 AM »
Quote from: Rick81 on January 10, 2025, 07:58:55 PM
I'm glad it worked out. I've also got the Vag kkl cable and carnt get the program to read. How long did you leave the boot pin on for. Or should I say what did you do

hi i count the 5 seconds and took it off.

i miss typed the cable i used - it is a red vag kkl one and in device manager it said serial cable, not ch340.

https://www.aliexpress.com/item/1005006340238053.html?spm=a2g0o.productlist.main.1.2021176dCHMUau&algo_pvid=e42d5ab1-cb4c-4aea-a39f-284decdde767&algo_exp_id=e42d5ab1-cb4c-4aea-a39f-284decdde767-0&pdp_npi=4%40dis%21GBP%215.52%215.52%21%21%216.59%216.59%21%40211b441e17366078213983475efe8e%2112000036818836141%21sea%21UK%212631887398%21X&curPageLogUid=EjhFZp5irVyQ&utparam-url=scene%3Asearch%7Cquery_from%3A like this.

this connected straight away, where as the two blue kkl i have kept giving the the same error.
Logged
Pages: 1 ... 62 63 [64]
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • March 14, 2025, 03:50:16 PM
  • Welcome, Guest. Please login or register.
    Did you miss your activation email?

    Login with username, password and session length
Search
 
Advanced Search
About Disclaimer
All Rights Reserved 2010 Nefarious Motosports
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.067 seconds with 18 queries. (Pretty URLs adds 0s, 0q)