Pages: 1 2 [3]
Author Topic: Error when attempting to read Allroad ECM.  (Read 19195 times)
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12233


WWW
« Reply #30 on: February 22, 2017, 02:09:10 PM »

I then ran it on my 4.2 EEPROM dump (1024 bytes) and unfortunately the program only works on 512 sized EEPROMS. It reported "file must be 512 bytes."

You don't need any other tool except the ability to truncate the file to 512 bytes.

your clue is here in your very own post:

It's worth noting that my EEPROM on my 4.2L is a SP08C3 and is 1024 bytes.  When I look at the BIN in a hex editor, 513-1024 is just all FF's.  There's no data in that section of memory.

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.
SteveAR
Full Member
***

Karma: +4/-1
Offline Offline

Posts: 103


« Reply #31 on: February 22, 2017, 03:43:29 PM »

Fair enough, I figured the down and dirty way was to use my hex editor to create a BIN file of just the lower 512 of my 1024 dump. The only area with real data.   Make changes to that, run that through the checker tool and then put that back into the original 1024 byte BIN.     My understanding from reading is that in a 512 byte file, there's 32 addresses(?) each with 16 bytes.  the first 14 bytes are data and the last two are the checksum.   At work if I read or flash a file to an IC, there's a single checksum for the entire contents of the chip.  Is this so with what I'm working with and is the ECM also checking that?  If I modify just the lower 512 and leave the upper 512 alone, the checksum for the entire file will have changed.  Whether that's relevant or checked by the system I don't know.

As I said I would eventually like to put a 512 byte chip on my ECM but for the time being I want to leave the 1024 byte chip in place.  I don't know why they used it and don't want to create a problem for myself.  I assume it was because the 512 went obsolete or they had trouble getting it.  But, blank or not, in case the ECM is looking to verify the upper 512 I want to leave it in place.   Unless someone can confirm that part of the memory is ignored.
Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12233


WWW
« Reply #32 on: February 22, 2017, 04:42:21 PM »

Unless someone can confirm that part of the memory is ignored.

It is ignored.
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.
SteveAR
Full Member
***

Karma: +4/-1
Offline Offline

Posts: 103


« Reply #33 on: February 22, 2017, 05:14:20 PM »

OK thank you for this info.  I was able to copy the lower 512 of my EEPROM dump into its own .bin file, make VIN/SKC/IMMO ID/Cluster ID changes to that file, run through checksum corrector and verify the data changed via the 95040tool --status output.   I copied the lower 512 back into my 1024 BIN and flashed it to the ECM.  It will still be nothing short of a miracle if it works but i'm hopeful. 
  I still can't find any info on changing the soft coding of the ECM from a auto to a manual.   The 4.2L Allroad was never offered as a manual so I'm still slogging through that challenge.  I know that on the 2.7T, you change the software coding from 07755 to 07715 (where 5=auto and 1=manual) but when I try and change my 4.2L/Auto ECM softcoding in the same manner, it reports an "out of range" error.  Stock software coding is 0007755.  I tried coding it to 0007715 with VCDS and it returned the "out of range" error. (I logged in with the SKC)
   Someone passed this post to me and I emailed the two gentlemen (PRJ and DDillenger) who claim they've handled this before......

http://nefariousmotorsports.com/forum/index.php?topic=3636.0title=
Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12233


WWW
« Reply #34 on: February 22, 2017, 05:19:08 PM »

I wish I could help you there but I have no 4.2 AR experience :/
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.
SteveAR
Full Member
***

Karma: +4/-1
Offline Offline

Posts: 103


« Reply #35 on: February 22, 2017, 05:58:06 PM »

No Problem, thanks for the help. I'm much closer than I've ever been.  Hoping to hear back from one of those guys.  Or I may need to flash the ECM (main flash/tune) with a file from a car that offered both an Auto and Manual.  EG a B6S4.  That car has the same exact motor as the 4.2L Allroad but because it was an S4 they also offered a 6MT.  I have a ECM from that exact car coming in the mail (EBAY) so I can examine the soft coding.  Also maybe read the main flash off of it and copy it to my Allroad ECM.  Or leave the EBAY ECM as-is and update the VIN/SKC/IMMO/CLUSTER info. I'll have several options to try when I pull the trigger on this swap which should be in the next couple weeks.....
Logged
AARDQ
Sr. Member
****

Karma: +11/-0
Offline Offline

Posts: 338


« Reply #36 on: February 23, 2017, 08:07:05 AM »

If it was never offered as a manual, most likely soft coding isn't going to work.  DDillinger passed away last year.

You might reach out to Nubcake if prj isn't available; he's done similar work with the RS6.
Logged
SteveAR
Full Member
***

Karma: +4/-1
Offline Offline

Posts: 103


« Reply #37 on: February 23, 2017, 08:57:51 AM »

Very sorry to hear that. I guess none of us are guaranteed a tomorrow.
I do hope to hear back from PRJ , I sent him a PM. Thanks for the suggestion of Nubcake.  I will send him something as well.    It was my fear that soft coding wouldn’t work for the reason you stated.  And my best guess at the soft coding got rejected by the ECM (out of range!) so likely that confirms it. I have higher hopes that I can grab the factory baseline/flash off my B6S4 ECM and use that. Chomping at the bit for that to arrive.  Or just use that ECM period. (after matching the SKC/VIN/IMMO/Cluster info)  We shall see.  I still have my fall-back plan of contacting JHM. 
Logged
Pages: 1 2 [3]
  Print  
 
Jump to:  

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