BoostedR36MK3
Newbie
Karma: +0/-0
 Offline
Posts: 9
|
 |
« on: May 05, 2011, 01:05:45 AM »
|
|
|
I pulled this flash off a car tonight and then ran ME7Checker and it shows 1 error. The file has not been touched since pulled from the ECU. This is a GIAC file. I was wondering how to find out what the error is if there is actually something wrong with it. The car runs fine so I am not sure if I got a bad read or if ME7Checker is showing a false error.
ME7Check v1.08 (c) mki, 06/2004-04/2011
Checking file giac 04 1.8t\entire flash\giac 04 1.8t.bin (size=1048576)
Reading Version Strings...
-> Bootrom Version = 05.12
-> EPK = 42/1/ME7.5/120/4013.00//24D/Dst03o/051202/
-> Contents of ECUID data table:
- '0261208163' (SSECUHN)
- '1037367967' (SSECUSN)
- '06A906032NK ' (VAG part number)
- '0003' (VAG sw number)
- '1.8L R4/5VT ' (engine id)
-> Contents of ECUID data table:
- 'HW_MAN004'
-> Found 1 errors!!! *******************************
|
|
|
|
|
Logged
|
|
|
|
orienz
Full Member
Karma: +12/-2
Offline
Posts: 113
|
|
« Reply #1 on: May 05, 2011, 03:23:59 AM »
|
|
|
Strange, maybe GIAC moved stuff around and got the file "incompatible" with Me7check? Just a guess. Is this file for k04 upgrade? List some car mods.
|
|
|
|
|
Logged
|
|
|
|
Matt Danger
Full Member
Karma: +17/-1
Offline
Posts: 116
|
|
« Reply #2 on: May 05, 2011, 09:19:01 AM »
|
|
|
If maps are moved ME7Check may not know the location of checksums and will output errors.
|
|
|
|
|
Logged
|
|
|
|
BoostedR36MK3
Newbie
Karma: +0/-0
Offline
Posts: 9
|
|
« Reply #3 on: May 05, 2011, 09:32:38 AM »
|
|
|
Its for the K03. Car has front mount, inlet pipe, forge 007, N75J, CAI, 2.5APR Exhaust from turbo back, LS. I think it also has a 4bar FPR.I can't remember everything else. We were installing the K04 and larger exhaust manifold last night and he will have the ecu flashed for the K04 but he has a fried ECU that I had to swap out before so I was going to use this dead ECU to test on and learn to tune a little. This flash was pulled from the good ECU. The bad one does not allow throttle is all. I am sure the O2 circuits are dead also. The car does start and run with it though so I would know if I screwed the file. Just wanted to make sure I was starting with a good file first.
|
|
|
|
|
Logged
|
|
|
|
|
gremlin
|
|
« Reply #4 on: May 05, 2011, 03:55:36 PM »
|
|
|
-> EPK = 42/1/ME7.5/120/4013.00//24D/Dst03o/051202/
-> Contents of ECUID data table:
- '0261208163' (SSECUHN)
- '1037367967' (SSECUSN)
- '06A906032NK ' (VAG part number)
- '0003' (VAG sw number)
What is clear to view according EPK data base number (marked red) that GIAC hide real ECUID table data  Real ECUID for this file is as fpllows: '0261208188' (SSECUHN) '1037366517' (SSECUSN) '06A906032PL ' (VAG part number) '0003' (VAG sw number) |
|
|
|
|
Logged
|
|
|
|
|
mtx-electronics
|
|
« Reply #5 on: May 05, 2011, 03:57:02 PM »
|
|
|
Out of curiosity I did a quick check on the file and found 2 checksum errors.
P.S. There is something strange about this file... It seems as if there are missing data tables... Anyone else have the same impression?
P.S.S. Looked a bit deeper into it and they are not missing, this bin file does not use them so there are a lot less checksum zones.
|
|
|
|
« Last Edit: May 05, 2011, 04:13:13 PM by mtx-electronics »
|
Logged
|
|
|
|
BoostedR36MK3
Newbie
Karma: +0/-0
Offline
Posts: 9
|
|
« Reply #6 on: May 05, 2011, 04:10:00 PM »
|
|
|
-> EPK = 42/1/ME7.5/120/4013.00//24D/Dst03o/051202/
-> Contents of ECUID data table:
- '0261208163' (SSECUHN)
- '1037367967' (SSECUSN)
- '06A906032NK ' (VAG part number)
- '0003' (VAG sw number)
What is clear to view according EPK data base number (marked red) that GIAC hide real ECUID table data Real ECUID for this file is as fpllows: '0261208188' (SSECUHN) '1037366517' (SSECUSN) '06A906032PL ' (VAG part number) '0003' (VAG sw number) The part number is actually NK at the end. I know that from when I swapped the ECU's. |
|
|
|
|
Logged
|
|
|
|
orienz
Full Member
Karma: +12/-2
Offline
Posts: 113
|
|
« Reply #7 on: May 05, 2011, 04:16:12 PM »
|
|
|
They just changed file id to NK, essentially the file is PL version. I noticed that lots of tuners do this but it's like they know what variations of ECUs are compatible with each other. ECUX is the same way tho', their "ECU property files" are grouped.
I might buy one used ECU just to see if I can flash any ME7.5 file to it.
|
|
|
|
|
Logged
|
|
|
|
|
julex
|
|
« Reply #8 on: May 05, 2011, 04:54:28 PM »
|
|
|
I can run this file in my tunerpro and give you checksummed version so that you can compare... I can also give you APR (haha) file too.
|
|
|
|
|
Logged
|
|
|
|
|
gremlin
|
|
« Reply #9 on: May 05, 2011, 05:19:47 PM »
|
|
|
P.S. There is something strange about this file... It seems as if there are missing data tables... Anyone else have the same impression?
Nothing strange... A big part of tuned calibration maps are shifted from normal place and encrypted. Also added custom executive code to access new calibration and decrypt to raw view. It's normal and protect tuned file from "copy&paste" tuners |
|
|
|
|
Logged
|
|
|
|
BoostedR36MK3
Newbie
Karma: +0/-0
Offline
Posts: 9
|
|
« Reply #10 on: May 05, 2011, 05:33:21 PM »
|
|
|
P.S. There is something strange about this file... It seems as if there are missing data tables... Anyone else have the same impression?
Nothing strange... A big part of tuned calibration maps are shifted from normal place and encrypted. Also added custom executive code to access new calibration and decrypt to raw view. It's normal and protect tuned file from "copy&paste" tuners So is there no error in the file and ME7Checker says there is because the file is altered by GIAC? |
|
|
|
|
Logged
|
|
|
|
|
gremlin
|
|
« Reply #11 on: May 05, 2011, 05:42:40 PM »
|
|
|
So is there no error in the file and ME7Checker says there is because the file is altered by GIAC?
Can say only ... maybe No problem to try this file, but don't wonder if ECU will "locked" after aprox 20 miles drive and ingnition off. |
|
|
|
|
Logged
|
|
|
|
setzi62
Full Member
Karma: +142/-0
Offline
Posts: 249
|
|
« Reply #12 on: May 06, 2011, 02:40:28 AM »
|
|
|
In the file "giac 04 1.8t.bin" the overall program checksum is not updated.
If you are not facing problems with this file, this checksum is probably not really used
by the ECU during runtime. Besides this, everyting else regarding the checksums
is as usual and fine in the file.
The overall program checksum is calculated as wordwise (2byte) sum of the ranges
80'0000 - 80'FBFF and 82'0000 - 8F'FFFF into a long (4 byte) variable.
You find the resulting checksum always stored at the end of the flash memory,
e.g. at 8F'FFE0 (file offset 0xfffe0) and the inverted checksum at 8F'FFE4 (file offset 0xfffe4)
for 1MB flash.
|
|
|
|
|
Logged
|
|
|
|
|
