Pages: [1] 2 3
Author Topic: Dove straight in  (Read 22574 times)
b3n4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 23


« on: December 13, 2014, 04:30:16 PM »

So I decided that it would be a good idea to try and read the ECU on my '03 allroad tip. Low and behold it didnt want to start up after I finished reading the ECU file. It has a 4Z7 907 551 S ECU file on it and I have since read that a 4Z7 907 551 R might remedy this.  I found a stock 4Z7 907 551 R file on nyets' server but when running a checksum on it with MECHECK it gets an 1 error. What should I start looking into next?

Thanks
Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12268


WWW
« Reply #1 on: December 13, 2014, 04:37:34 PM »

==============================================================================
ME7Check v1.12 (c) mki, 06/2004-05/2012
Checking file bins/4Z7907551R.bin (size=1048576)
Reading Version Strings...
-> Bootrom Version = 06.02
-> EPK = 42/1/ME7.1.1/5/6030.03//25A/DstU2o/200602//
-> Contents of ECUID data table:
   - '0261207769'         (SSECUHN)
   - '1037366370'         (SSECUSN)
   - '4Z7907551R  '       (VAG part number)
   - '0003'               (VAG sw number)
   - '2.7L V6/5VT    '    (engine id)
-> Contents of ECUID data table:
   - 'HW_MAN004'


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

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

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 ex
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12268


WWW
« Reply #2 on: December 13, 2014, 04:38:20 PM »

ME7Tool (v1.0.3) [Management tool for Bosch ME7.x firmwares]
Inspiration from Andy Whittaker's tools and information.
Written by 360trev and nyet [BSD License Open Source].

Attempting to open firmware file 'bins/4Z7907551R.bin'

Step #1: Reading ROM info ..
 Searching for EPK signature...OK
 Searching for ECUID table...OK
 EPK         : '42/1/ME7.1.1/5/6030.03//25A/DstU2o/200602//'
 Part Number : '4Z7907551R  '
 Engine ID   : '2.7L V6/5VT    '
 SW Version  : '0003'
 HW Number   : '0261207769'
 SW Number   : '1037366370'

Step #2: Reading ROMSYS ..
 Startup section: word[0x008000]+word[0x00FFFE]
 @008038 Add=0x004AEB CalcAdd=0x004AEB  ADD OK
 Program pages: 8k page first+last in 0x0000-0xFFFF and 0x20000-0xFFFFF
 @00803c Add=0x99D4E0 CalcAdd=0x99D4E0  ADD OK
 All param page: word[0x010000]+word[0x01FFFE]
 @01e182 Add=0x00971D CalcAdd=0x00971D  ADD OK

Step #3: Reading RSA signatures ..
 Searching for RSA offset #0...OK
 Searching for RSA offset #1...OK
         Signature: @ab6a0-ab720
           Modulus: @16a94-16b14
          Exponent: @16b14 = 3
 Searching for MD5 ranges...OK
 MD5 Block Offset Table @16a70 [32 bytes]:
 1) 0x00010002-0x00013FFE
 2) 0x00014382-0x00017F4E
 3) 0x00018192-0x0001FBDC
 4) 0x00026A00-0x0002FFFC
 EncrMD5: 8f 35 55 cf 75 03 00 0c a4 3a 2d 8a 3a 3b 65 77
 CalcMD5: 8f 35 55 cf 75 03 00 0c a4 3a 2d 8a 3a 3b 65 77
  OK

Step #4: Finding CRC table(s) ..
 Searching for CRC table(s)...OK
 CRC table(s) OK

Step #5: Reading Main Data Checksums ..
 Searching for main data CRC pre block...missing
 Searching for main data CRC/csum blocks...OK
 Searching for main data CRC offsets...missing
 Searching for main data checksum offsets...OK
 Main Checksums:
 1) 0x010002-0x013FFE CalcCSM: 001277ED
 2) 0x014382-0x017F4E CalcCSM: 0029BE45
 3) 0x018192-0x01FBDC CalcCSM: 0047A323
 4) 0x026A00-0x02FFFC CalcCSM: 00A68EF3
 @abee6 CSM: 00A68EF3 CalcCSM: 00A68EF3  Main data checksum OK

Step #6: Reading Main Program Checksums ..
 Searching for main program checksum..OK
 ROM Checksum Block Offset Table @27f90 [16 bytes]:
 1) 0x000000-0x00FBFF CalcChk: 475476BA
    0x00FC00-0x01FFFF CalcChk: 23D54E4C CalcCRC: 04156E6A SKIPPED
 2) 0x020000-0x0FFFFF
    <fffe0>  Chk: A58029FE CalcChk: A58029FE OK (i)

Step #7: Reading Multipoint Checksum Blocks ..
 Searching for multipoint block descriptor #1...missing
 Searching for multipoint block descriptor #2...OK
 1) <1fbde>  0x000000-0x003FFF Chk: 0E59D5C8 Boot: (whitelisted) OK
 2) <1fbee>  0x004000-0x007FFF Chk: 1077FB35 Boot: (whitelisted) OK
 3) <1fbfe>  0x000000-0x003FFF Chk: 0E59D5C8 CalcChk: 0E59D5C8 OK
 4) <1fc0e>  0x004000-0x007FFF Chk: 1077FB35 CalcChk: 1077FB35 OK
 Multipoint #2: [66 blocks x <16> = 1056 bytes]

*** Found 70 checksums in bins/4Z7907551R.bin

*** DONE! 0 error(s) in bins/4Z7907551R.bin! ***
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

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 ex
b3n4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 23


« Reply #3 on: December 13, 2014, 05:17:23 PM »

When I run ME7Check I get 1 error but I seem to have an older version than you. me7sum says no errors so went out to try and flash the bin, but I can no longer connect to the ecu through nefmoto. VCDS connects through OBD but not the controller module. Is this looking like I'll have to do a bench flash? I got the galleto cable in yesterday which sort of spured my ambition today.
Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12268


WWW
« Reply #4 on: December 14, 2014, 12:55:55 AM »

When I run ME7Check I get 1 error but I seem to have an older version than you.

http://nefariousmotorsports.com/forum/index.php?topic=447.0title=
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

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 ex
b3n4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 23


« Reply #5 on: December 14, 2014, 12:42:04 PM »

Thanks I had incorrectly downloaded a previous version from the post there. I removed my ECU but am currently having issues getting it into boot mode. I'm trying to uninstall all the drivers and load new ones in any common issues with ME7.1.1 ecus that I might be overlooking here?
Thanks
Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12268


WWW
« Reply #6 on: December 15, 2014, 11:27:09 AM »

Thanks I had incorrectly downloaded a previous version from the post there.

Yea setzi's version numbering scheme is kinda confusing.

Quote
I removed my ECU but am currently having issues getting it into boot mode. I'm trying to uninstall all the drivers and load new ones in any common issues with ME7.1.1 ecus that I might be overlooking here?

Yes.

Sometimes you need to lower baud rate.

Some ME7.1.1 can be tricky to get into bootmode.

They can be finicky.
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

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 ex
b3n4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 23


« Reply #7 on: December 15, 2014, 05:49:20 PM »

Is there any benefit to grounding pin 24 with a resistor? I've seen that said a couple times.
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #8 on: December 15, 2014, 11:53:23 PM »

Is there any benefit to grounding pin 24 with a resistor? I've seen that said a couple times.

If you slip you are less likely to kill the ecu.
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
b3n4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 23


« Reply #9 on: December 16, 2014, 05:31:49 PM »

I'm having the worst time trying to get the galletto cable I have to work I've tried both Windows 7 and xp now. It keeps coming up as EOBD2 under unkown devices in device manager. I have installed the ftdi drivers from the website and when I try to point windows to the directory of the drivers it tells me there are no valid drivers in there. I had it working for a bit on Windows 7 but my computer crashed and it stopped working. I am getting really confused by all this and I can't view the cable with m-prog to check the serial number.
Logged
b3n4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 23


« Reply #10 on: December 16, 2014, 06:57:16 PM »

I'm just wondering originally I flashed an incorrect bin to my ecu its was an 8bo not a 4zy bin and that's what started my communication errors. Could it be that this ecu is toast? I tried using a Ross tech cable with  nefmoto and after I think I've placed the ecu in boot mode nefmoto cannot connect. If someone could lend some input here it would be much appreciated. I'm going to grab a couple new ecus but will have to figure out this boot mode situation in order to remove the immo. Currently have a pretty big paper weight holding the driveway down.
Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12268


WWW
« Reply #11 on: December 17, 2014, 12:42:10 AM »

I'm just wondering originally I flashed an incorrect bin to my ecu its was an 8bo not a 4zy bin and that's what started my communication errors. Could it be that this ecu is toast? I tried using a Ross tech cable with  nefmoto and after I think I've placed the ecu in boot mode nefmoto cannot connect. If someone could lend some input here it would be much appreciated. I'm going to grab a couple new ecus but will have to figure out this boot mode situation in order to remove the immo. Currently have a pretty big paper weight holding the driveway down.

Nefmoto cannot program in bootmode. You'll have to use galletto.
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

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 ex
b3n4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 23


« Reply #12 on: December 17, 2014, 05:05:22 AM »

I thought so but I'm not sure if its me, my computer, or my galletto cable but I can't seem to figure out the driver install for it. Windows just says unrecognized device even after I've installed the FTDI signed drivers. The weirdest part was that the cable was recognized briefly on my system until everything crashed and it disappeared again. I think once I can figure this out I'll be in better shape.
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #13 on: December 17, 2014, 05:37:59 AM »

There were instances of windows killing cloned FTDI chips. That is reportedly over, but........

Use the drivers in the "Galletto edited with proper english" sticky.
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
b3n4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 23


« Reply #14 on: December 17, 2014, 08:42:41 AM »

Ok I'll give that a shot when I'm home from work. Think I may stock up on some cables as well.
Logged
Pages: [1] 2 3
  Print  
 
Jump to:  

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