Pages: [1]
Author Topic: ME7Check - 3 Errors - Just Read in Bootmode  (Read 6617 times)
Currancchs
Newbie
*

Karma: +9/-0
Offline Offline

Posts: 20


« on: April 15, 2013, 06:01:31 PM »

Hi guys,

I'm new here and trying to learn. I finally was able to read the flash off of my 2001 Audi TT 225 AMU (400BB memory layout, 8N0906018T ECU) using Galletto in boot mode. After pulling the flash off, I ran it through ME7Check, which came back with 3 errors... I just read it! Is this normal?

Also, I have read that if you get a certain checksum failed code from improperly flashing back to the ECU that you have to use the nefmoto software (or something using KWP1281/2000) to reset the checksum error... Well apparently my ECU can only be read via Galletto in bootmode. If I was to screw up, is the ECU forever bricked or is there a way to recover?

Eventually I want to remove the SAI code and set readiness for that system, but until I'm confident reading and writing I'm not going any further.

Note: This was done on a bench harness using a power supply regulated to ~12.5 volts. I had previously set it to 13.1 volts, but this caused read errors... It seemed to pull ~205mA normally, and ~166mA in boot mode, fluctuating between 160-240mA during read.

Thanks,
Matt
Logged
ddillenger
Hero Member
*****

Karma: +639/-21
Offline Offline

Posts: 5640


« Reply #1 on: April 15, 2013, 07:32:56 PM »

The reason you had to read it in bootmode, and the errors are related. I'd be willing to bet you have an APR (or other mainstream) file on your hands. Open it with a hex editor and look for ASCII (Text) strings.

As for clearing the checksum DTC, it can be done by manually editing the eeprom (95040) contents. Take a look at the immobilizer sticky, and scroll down to the "death code".
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
Currancchs
Newbie
*

Karma: +9/-0
Offline Offline

Posts: 20


« Reply #2 on: April 16, 2013, 07:23:46 AM »

The reason you had to read it in bootmode, and the errors are related. I'd be willing to bet you have an APR (or other mainstream) file on your hands. Open it with a hex editor and look for ASCII (Text) strings.

As for clearing the checksum DTC, it can be done by manually editing the eeprom (95040) contents. Take a look at the immobilizer sticky, and scroll down to the "death code".

The file is definitely stock. I do have an additional ECU with APR software (that's in the car now), but it had the rear O2 sensors deleted by APR, then I removed the SAI system, so it won't pass inspection, hence why I'm playing around with my stock ECU. I have seen the ASCII strings in GIAC files before, and nothing like that in this one.

So, just to be clear, you WILL cause checksum errors in the read file when reading in boot mode? If I never wrote anything to the ECU, would the ECU itself now have checksum issues?

Thank you for pointing me to the "death code" immobilizer section, I will look into that.

Extra Info - I had tried using ArgDub's tool to read the EEPROM previously, but wound up getting an error at the portion where it was loading monitor services (or something like that). This was at the slightly higher voltage which had failed with Galletto. I never tried again after a successful Galletto boot mode read. I also didn't play around with lower baud rate settings. I will try tonight to read the EEPROM and store a working copy (hopefully it doesn't already have an error). If I have both the EEPROM read and the stock flash bin, would writing these both back to a bricked ECU (assuming they are error free) fix any potential future death code issues (I just want to make sure I have a proven tested way to restore from the worst case scenario before going further)? Also, would the death code show up if I ran VCDS on the bench, conversely, if it doesn't show up, but ME7Check shows 3 errors, is there a difference between my bin on my pc and the bin on the ECU? Does this mean bootmode does not read a true exact copy?

Sorry for my newbishness. I really appreciate everybody's help here, between helping me directly and just documenting these things to allow people like me to learn through the archives and trials of others.

I started reading about the Death Code issue (thanks for the thorough writeup ddilenger!) but need to dedicate more time to really absorb the material.

p.s., here is the file in case you would like to take a look.
« Last Edit: April 16, 2013, 09:20:36 AM by Currancchs » Logged
ddillenger
Hero Member
*****

Karma: +639/-21
Offline Offline

Posts: 5640


« Reply #3 on: April 16, 2013, 11:18:36 AM »

I see no checksum errors n that file, verified with both me7check and winols.

As for boomode causing a checksum error, it will not.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
Currancchs
Newbie
*

Karma: +9/-0
Offline Offline

Posts: 20


« Reply #4 on: April 16, 2013, 11:21:33 AM »

I see no checksum errors n that file, verified with both me7check and winols.

As for boomode causing a checksum error, it will not.

OK. That's great to hear. Thank you for running that, I'm not sure how I screwed up just checking checksums... Oh well, more reading to be done.

Just reran the file through ME7Check_190411 (albeit on a macbook pro on OSX, running through wine), but the error appears the same, I'm sure that I am just doing something stupid though... The screenshot is attached.
« Last Edit: April 16, 2013, 11:26:42 AM by Currancchs » Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-167
Offline Offline

Posts: 12236


WWW
« Reply #5 on: April 16, 2013, 11:26:10 AM »

copy and paste the output of the command line.

please don't take a screen shot, just copy/paste the text.
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
Currancchs
Newbie
*

Karma: +9/-0
Offline Offline

Posts: 20


« Reply #6 on: April 16, 2013, 11:27:26 AM »

copy and paste the output of the command line.

please don't take a screen shot, just copy/paste the text.

Oops, sorry, just attached a screenshot, here is the text:

ME7Check v1.08 (c) mki, 06/2004-04/2011
Checking file /Users/matthewcurran/Desktop/Audi TT 1.8T AMU 225HP 6sp 29F400BB 8N0906018T.bin (size=524288)
Reading Version Strings...
-> Bootrom Version = embedded in CPU, asume 05.12/05.32
-> EPK = 42/1/ME7.5/5/4018.00//F22id/Dst03o/180200/
-> Contents of ECUID data table:
   - '0261206228'         (SSECUHN)         
   - '1037354508'         (SSECUSN)         
   - '8N0906018T  '       (VAG part number)
   - '0003'               (VAG sw number)   
   - '1.8L R4/5VT     '   (engine id)       

-> Found 3 errors!!!   *******************************
Logged
ddillenger
Hero Member
*****

Karma: +639/-21
Offline Offline

Posts: 5640


« Reply #7 on: April 16, 2013, 11:42:11 AM »

==============================================================================
ME7Check v1.12 (c) mki, 06/2004-05/2012
Checking file C:\Documents and Settings\User1\My Documents\Downloads\Audi TT 1.8
T AMU 225HP 6sp 29F400BB 8N0906018T.bin (size=524288)
Reading Version Strings...
-> Bootrom Version = embedded in CPU, asume 05.12/05.32
-> EPK = 42/1/ME7.5/5/4018.00//F22id/Dst03o/180200/
-> Contents of ECUID data table:
   - '0261206228'         (SSECUHN)
   - '1037354508'         (SSECUSN)
   - '8N0906018T  '       (VAG part number)
   - '0003'               (VAG sw number)
   - '1.8L R4/5VT     '   (engine id)

-> No errors found. File is OK.   *********************
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
nyet
Administrator
Hero Member
*****

Karma: +604/-167
Offline Offline

Posts: 12236


WWW
« Reply #8 on: April 16, 2013, 11:45:20 AM »

ME7Check v1.08 (c) mki, 06/2004-04/2011

ME7Check v1.12 (c) mki, 06/2004-05/2012

Smiley
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
Currancchs
Newbie
*

Karma: +9/-0
Offline Offline

Posts: 20


« Reply #9 on: April 16, 2013, 12:23:13 PM »

Thank you ddilinger/nyet!
Logged
Pages: [1]
  Print  
 
Jump to:  

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