NefMoto > Technical > Cluster and Immobilizer (Moderator: ddillenger) > anyone ever work out what FAIL 0x07 or 0x01 means?
Pages: [1] 2
« previous next »
Author Topic: anyone ever work out what FAIL 0x07 or 0x01 means?  (Read 11310 times)
paulazoid
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 12
« on: June 05, 2014, 01:02:24 PM »
I've wasted the best part of a day attempting to read and dump the eeprom Fail (error 0x01)

then I removed the instrument panel fuse and got FAIL (error 0x07)

Think I may be close to setting fire to my car

Has anyone ever worked out what errors 0x07 or 0x01are and how to solve them?
Logged
groveguy89
Jr. Member
**

Karma: +0/-1
Offline Offline

Posts: 31
« Reply #1 on: January 31, 2016, 02:57:03 AM »
Sorry for bringing up what appears to be a dead thread but I'm currently dealing with this same issue and this thread was the only reference I could find relating to this error. ECU seems to be successfully placed in bootmode, as it no longer connects via OBD, but fails to allow me to read the EEPROM no matter what options I change around with the 95040 tool. Also just realized he was trying to read in-car, and I'm using a bench setup. If the OP ever figured out a solution or if anyone else has any suggestions they would be greatly appreciated. Smiley
Logged
adam-
Hero Member
*****

Karma: +122/-33
Offline Offline

Posts: 2178
« Reply #2 on: January 31, 2016, 06:46:38 AM »
Can you write a file with bootmode active?  With Galletto?
Logged
groveguy89
Jr. Member
**

Karma: +0/-1
Offline Offline

Posts: 31
« Reply #3 on: January 31, 2016, 10:06:14 PM »
Quote from: adam- on January 31, 2016, 06:46:38 AM
Can you write a file with bootmode active?  With Galletto?

     I should have mentioned what I'm using I suppose. I have a home made bench harness and a Ross Tech HEX-CAN USB that I'm using for my FTDI interface, apparently my eBay cable died yesterday. I have not tried using the Galletto yet I've never had an issue using ArgDub's tool.
     I was able to successfully get it to read the 95040 via OBD on the bench now, but still get the same errors whenever I try to read or write in bootmode. When in "bootmode"or what should be bootmode neither ME7 Flasher or 95040 1.31 can connect via OBD but for some reason the ECU still doesn't seem to want to respond.


VIA OBDD:\Documents and Settings\Admin\Desktop\me7_95040_v1.31>me7_95040 --OBD -rp2 950
40.bin
Ver: 1.31
Com Port: 2
Baud Rate: 10400
Opening COM2 ... OK
Initiating communication ... OK
ECU ID response: 4B0907551P
                 2.7l V6/5VT     G
                 0002
                 SoftCod: 06712, WSC: 02325
Reading EEPROM ............................................................... O
K
File saved
Closing COM2

VIA "bootmode"D:\Documents and Settings\Admin\Desktop\me7_95040_v1.31>me7_95040 --bootmode -p2
 --screen
Ver: 1.31
Com Port: 2
Baud Rate: 10400
Opening COM2 ... OK
Starting Boot_mode ... FAIL ... No response from ECU. (error=0x07)
Closing COM2


D:\Documents and Settings\Admin\Desktop\me7_95040_v1.31>me7_95040 --bootmode -wp
2 95040.bin
Ver: 1.31
Com Port: 2
Baud Rate: 10400
Opening COM2 ... OK
Starting Boot_mode ... FAIL ... No response from ECU. (error=0x07)
Closing COM2

D:\Documents and Settings\Admin\Desktop\me7_95040_v1.31>me7_95040 --OBD -rp2 950
40.bin
Ver: 1.31
Com Port: 2
Baud Rate: 10400
Opening COM2 ... OK
Initiating communication ... FAIL. (error=0x07)
Closing COM2

D:\Documents and Settings\Admin\Desktop\me7_95040_v1.31>me7_95040 --bootmode -rp
2 -b 57600 95040.bin
Ver: 1.31
Com Port: 2
Baud Rate: 57600
Opening COM2 ... OK
Starting Boot_mode ... FAIL ... No response from ECU. (error=0x07)
Closing COM2

D:\Documents and Settings\Admin\Desktop\me7_95040_v1.31>me7_95040 --bootmode -rp
2 95040.bin
Ver: 1.31
Com Port: 2
Baud Rate: 10400
Opening COM2 ... OK
Starting Boot_mode ... FAIL ... No response from ECU. (error=0x07)
Closing COM2

D:\Documents and Settings\Admin\Desktop\me7_95040_v1.31>me7_95040 --bootmode -rp
2 -b 9600 95040.bin
Ver: 1.31
Com Port: 2
Baud Rate: 9600
Opening COM2 ... OK
Starting Boot_mode ... FAIL ... No response from ECU. (error=0x07)
Closing COM2

(I tossed in an attempt to read via OBD while it was in bootmode just to verify that it was indeed in bootmode, since I know that the OBD reading works)
Logged
prj
Hero Member
*****

Karma: +915/-427
Offline Offline

Posts: 5840
« Reply #4 on: February 01, 2016, 02:30:17 AM »
Ross tech cable will never work.
Logged
PM's will not be answered, so don't even try.
Log your car properly.
DT
Full Member
***

Karma: +20/-1
Offline Offline

Posts: 184
« Reply #5 on: February 01, 2016, 04:01:43 AM »
Cable with intelligent disabled and power to ECU and OBD/VCDS before starting up ECU should work better. If everything including VCDS cable get +12v simultaneous you get these problems.
Logged
Try ME7idatool http://nefariousmotorsports.com/forum/index.php?topic=21130.0
groveguy89
Jr. Member
**

Karma: +0/-1
Offline Offline

Posts: 31
« Reply #6 on: February 01, 2016, 07:44:31 AM »
Quote from: prj on February 01, 2016, 02:30:17 AM
Ross tech cable will never work.

Crap lol even with the VCP drivers for third party software support installed?
Edit-My local tuner just reconfirmed this lol guess I just assumed my 350$ cable would would work in place of my 12$ cable lmao. Back to eBay I go lol

Quote from: DT on February 01, 2016, 04:01:43 AM
Cable with intelligent disabled and power to ECU and OBD/VCDS before starting up ECU should work better. If everything including VCDS cable get +12v simultaneous you get these problems.


I was actually just debating revising my harness and now that you bring it up it has gone to the top of my list, considering I didn't mention that my setup supplied simultaneous power and you magically mention it haha. Thanks for the push in the right direction  Grin
« Last Edit: February 01, 2016, 09:05:56 AM by groveguy89 » Logged
prj
Hero Member
*****

Karma: +915/-427
Offline Offline

Posts: 5840
« Reply #7 on: February 01, 2016, 09:43:40 AM »
Quote from: DT on February 01, 2016, 04:01:43 AM
Cable with intelligent disabled and power to ECU and OBD/VCDS before starting up ECU should work better. If everything including VCDS cable get +12v simultaneous you get these problems.
Re-read what I wrote above. You clearly have not tried this.
Logged
PM's will not be answered, so don't even try.
Log your car properly.
groveguy89
Jr. Member
**

Karma: +0/-1
Offline Offline

Posts: 31
« Reply #8 on: February 01, 2016, 09:55:34 AM »
Quote from: prj on February 01, 2016, 09:43:40 AM
Re-read what I wrote above. You clearly have not tried this.

I still think his info is helpful as it will help me iron out any wrinkles and help get my flashing to be more consistent once I replace my FTDI cable. I really do appreciate the help guys, thank you.
Logged
DT
Full Member
***

Karma: +20/-1
Offline Offline

Posts: 184
« Reply #9 on: February 01, 2016, 11:58:22 AM »
Quote from: prj on February 01, 2016, 09:43:40 AM
Re-read what I wrote above. You clearly have not tried this.
I've probably missed something since you are so sure.
But this is what I verified 5min ago:  (With a genuine HEX+CAN VCDS cable)

Code:
C:\>ME7EEPROM_1.40.exe  -r -p2 --bootmode 95040 --CSpin P4.7 c:\test.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
Reading EEPROM ... OK
File saved
Closing COM2
Logged
Try ME7idatool http://nefariousmotorsports.com/forum/index.php?topic=21130.0
groveguy89
Jr. Member
**

Karma: +0/-1
Offline Offline

Posts: 31
« Reply #10 on: February 01, 2016, 08:23:00 PM »
Quote from: DT on February 01, 2016, 11:58:22 AM
I've probably missed something since you are so sure.
But this is what I verified 5min ago:  (With a genuine HEX+CAN VCDS cable)

Code:
C:\>ME7EEPROM_1.40.exe  -r -p2 --bootmode 95040 --CSpin P4.7 c:\test.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
Reading EEPROM ... OK
File saved
Closing COM2

Ok now I'm confused lol. So my VCDS cable will work? Also how did you get that nifty code window? It's much better than my ugly copy+paste.
Logged
gman86
Hero Member
*****

Karma: +45/-128
Offline Offline

Posts: 705
« Reply #11 on: February 01, 2016, 10:26:45 PM »
Quote from: groveguy89 on February 01, 2016, 08:23:00 PM
Ok now I'm confused lol. So my VCDS cable will work? Also how did you get that nifty code window? It's much better than my ugly copy+paste.

Code:
Wrap your pasted output in the [c0de] and [/c0de] tags (replace 0 with o)

Logged
groveguy89
Jr. Member
**

Karma: +0/-1
Offline Offline

Posts: 31
« Reply #12 on: February 01, 2016, 10:54:41 PM »
Quote from: gman86 on February 01, 2016, 10:26:45 PM
Code:
Wrap your pasted output in the [c0de] and [/c0de] tags (replace 0 with o)

Thank you Smiley I noticed you're using 1.40, that shouldn't make a difference though should it?


Logged
DT
Full Member
***

Karma: +20/-1
Offline Offline

Posts: 184
« Reply #13 on: February 02, 2016, 01:20:41 AM »
I don't think the version is important for the connection in bootmode but I think 1.31 lack the --CSpin to control communication to the eeprom.
Logged
Try ME7idatool http://nefariousmotorsports.com/forum/index.php?topic=21130.0
groveguy89
Jr. Member
**

Karma: +0/-1
Offline Offline

Posts: 31
« Reply #14 on: February 02, 2016, 04:10:40 AM »
Quote from: DT on February 02, 2016, 01:20:41 AM
I don't think the version is important for the connection in bootmode but I think 1.31 lack the --CSpin to control communication to the eeprom.

I was planning on going back to 1.40 for the CSpin funtionality, I was just using 1.31 to rule out the program being the cause. Now I'm excited to get back and fix my bench harness. Did you have to do anything special with drivers to use the Ross Tech cable or did you just use the VCP driver from their site?  Sorry for all the questions I just wanna be sure I'm not missing something. Thanks again for the help, it is greatly appreciated.
Logged
Pages: [1] 2
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • April 27, 2024, 06:11:43 AM
  • 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.025 seconds with 16 queries. (Pretty URLs adds 0s, 0q)