Risky
Full Member
Karma: +4/-0
 Offline
Posts: 107
|
 |
« Reply #750 on: November 12, 2018, 12:13:36 PM »
|
|
|
You can only read over obd with this tool, you can't write over obd. Take ECU out and put into bootmode. You can use the ftdi cable.
|
|
|
|
|
Logged
|
|
|
|
|
birchbark506
|
|
« Reply #751 on: November 12, 2018, 01:02:09 PM »
|
|
|
I have the ecu in bootmode, using same cable I use for galleto. I was able to read ecu eeprom in bootmode
|
|
|
|
|
Logged
|
|
|
|
Risky
Full Member
Karma: +4/-0
Offline
Posts: 107
|
|
« Reply #752 on: November 12, 2018, 04:52:36 PM »
|
|
|
Galletto never worked for me with this program. I use blue ftdi to flash eeprom and use same procedure as if you were going into boot mode with galletto. Might be worth a try.
|
|
|
|
« Last Edit: November 12, 2018, 08:52:20 PM by Risky »
|
Logged
|
|
|
|
|
birchbark506
|
|
« Reply #753 on: November 13, 2018, 04:01:26 AM »
|
|
|
This is the cheap kkl blue cable the same one i used for galleto is there maybe something I am doing wrong
|
|
|
|
|
Logged
|
|
|
|
Risky
Full Member
Karma: +4/-0
Offline
Posts: 107
|
|
« Reply #754 on: November 13, 2018, 08:14:33 AM »
|
|
|
Hmm take screenshot when you try to write.
|
|
|
|
|
Logged
|
|
|
|
|
birchbark506
|
|
« Reply #755 on: November 13, 2018, 11:44:59 AM »
|
|
|
I'll do that tonight once I am home and around the computer. Also the real ross tech cable will not work for this correct?
|
|
|
|
|
Logged
|
|
|
|
Risky
Full Member
Karma: +4/-0
Offline
Posts: 107
|
|
« Reply #756 on: November 13, 2018, 01:51:57 PM »
|
|
|
Idk if it would or not. Maybe in "dumb mode". Could try it.
You said you were using the ftdi cable for this tool as well as galletto. From my understanding you can only use blue ftdi if you change the cable serial number. If you did this did you happen to keep the FTDI serial number. This could possibly cause errors with the program...i would assume..but then again maybe not.
|
|
|
|
|
Logged
|
|
|
|
|
birchbark506
|
|
« Reply #757 on: November 14, 2018, 05:35:17 AM »
|
|
|
I remember editing the galleto software with hexeditor to make the cable read. I don't recall changing cable S/N
|
|
|
|
|
Logged
|
|
|
|
Risky
Full Member
Karma: +4/-0
Offline
Posts: 107
|
|
« Reply #758 on: November 14, 2018, 06:42:43 AM »
|
|
|
Oh okay good, screenshot when it fails to write... when you got time of course.
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #759 on: November 18, 2018, 09:11:32 PM »
|
|
|
The galletto binary always has to be hexedited to work with non-galletto cables, or the serial number of the cable has to be edited to match the required Galletto SN.
|
|
|
|
|
Logged
|
|
|
|
|
birchbark506
|
|
« Reply #760 on: November 19, 2018, 04:14:04 AM »
|
|
|
I kept the cable the S/N it came it. Only edit galleto software with hexeditor to match S/N from cable
|
|
|
|
|
Logged
|
|
|
|
heromanni
Newbie
Karma: +0/-0
Offline
Posts: 13
|
|
« Reply #761 on: November 24, 2018, 09:58:11 AM »
|
|
|
Did not find help trying to search the forum, how do I determine the chip select pin?
Microsoft Windows [versio 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Kaikki oikeudet pidätetään.
C:\>"C:\\ME7EEPROM" --bootmode 95040 -p 1 -b 9600 -w 95040immo_off.bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 9600
Memory type: 95040, size: 512
Opening COM1 ... OK
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 COM1
C:\>
Edit:
I tried with cs pin that was used in another 95040 and got this
Microsoft Windows [versio 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Kaikki oikeudet pidätetään.
C:\>"C:\\ME7EEPROM" --bootmode 95040 --CSpin P4.7 -p 1 -b 9600 -w 95040immo_off.
bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 9600
Memory type: 95040, size: 512
Chip Select pin: P4.7
Opening COM1 ... 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 COM1
C:\>
Edit 2
Seems like Immo is Off anyway, I put the ecu to car and no Immo Light, car starts fine.
|
|
|
|
« Last Edit: November 24, 2018, 10:51:47 AM by heromanni »
|
Logged
|
|
|
|
bignslow
Newbie
Karma: +0/-0
Offline
Posts: 15
|
|
« Reply #762 on: December 19, 2018, 10:00:26 AM »
|
|
|
What cable are you guys using to do this on the bench?
|
|
|
|
|
Logged
|
|
|
|
|
|
bignslow
Newbie
Karma: +0/-0
Offline
Posts: 15
|
|
« Reply #764 on: December 19, 2018, 11:36:52 AM »
|
|
|
Thanks. I did see links to these in another thread. I guess what I am not understanding is how do you hook that up to the ECU? I have MPPS cable which has individual pins that can be hooked up to the ECU. Does this cable need to be split open or just use alligator clips to connect? |
|
|
|
|
Logged
|
|
|
|
|
