|
Title: me7.1.1 boot mode ok - normal cant connect for DTC readout Post by: bkwrzdub on February 26, 2022, 07:57:54 AM uh
yeah so like the title says... I picked up a me7.1.1 box 4D0907560CL got it home, put it on my bench harness go to connect to readout DTC's..... nothing so... cover off, galletto it.... seems to bootmode okay? I however did see I do have the 000 jumper on the backside of the board and for these attemts DID NOT in fact desolder it. ECU data came back with Code: 0261207895 it SEEMS to read the ecu to file and it also seems to write.... after a few attempts. doing it CORRECTLY... ? no idea - probably not but when I get ECU data it now comes back with Code: 0261206373 so I think I did something incorrectly approx here maybe? the first read HW number indicates a 560CL... so that was correct? and the second HW number after the first write comes back as a 559D box for s6 4.2? and that's my goal - so that was maybe correct? still wont load normally to connect to readout DTC's ME7EEPROM can see it as Code: 0xC5 (C167 derivatives) but it fails on Chip_select pin err 0x70C01 or 0x70301 http://nefariousmotorsports.com/forum/index.php?topic=1369.msg104518#msg104518 I think I have the same scenario as ottosam so... what's the verdict here? not bad, but not good? the board isn't toast? I just put the wrong data on perhaps? can we salvage her? or do I need to find a new 7.1.1 box? I'm kind of in the same situation as 4loops here http://nefariousmotorsports.com/forum/index.php?topic=10024.0 looking to setup a 40v 4.2L from auto to manual Am I going about things in the proper manner? thx much chaps appreciate it! Title: Re: me7.1.1 boot mode ok - normal cant connect for DTC readout Post by: bkwrzdub on March 07, 2022, 08:07:08 PM Well, I managed to get both my ecu's to communicate more than just bootmode
I have a 4E0907560J and also a 4D0907560CL I understand I'm to read out the EEPROM on the flipside of the board which is a 5p08c3 - I've used argdub's tool to dump the bin successfully.... and I'm spelunking my way though a hex editor to look at it. I've gotten about this far and get a bit confused I see that there's posts saying the 5p08c3 chip cant be written with argdubs tool? then I've found this method http://nefariousmotorsports.com/forum/index.php?topic=11336.0 and ddillinger's 711off.bin listed here http://nefariousmotorsports.com/forum/index.php?topic=3317.0title= so then I use the eeprom tool http://nefariousmotorsports.com/forum/index.php?topic=6134.0 am I getting warmer? thanks all Title: Re: me7.1.1 boot mode ok - normal cant connect for DTC readout Post by: BlackT on March 07, 2022, 11:45:00 PM Read eeprom as 95040, immo off that file, do chc, write it as 95040
Title: Re: me7.1.1 boot mode ok - normal cant connect for DTC readout Post by: bkwrzdub on March 08, 2022, 06:57:17 AM Gotcha...
so even if the eeprom is a 5p08c3 / 95p08 dump it as a 95040.... hex it crc / checksum it write back as 95040 regardless of the filesize difference? (coz the other eeproms are supposed to be 512 bytes ?) right? I'll take a crack at it and report back much thanks! Title: Re: me7.1.1 boot mode ok - normal cant connect for DTC readout Post by: bkwrzdub on March 08, 2022, 07:24:04 AM used turboat's steps from this post
http://nefariousmotorsports.com/forum/index.php?topic=3319.0title= used me7eeprom, to dump... successfully used me7check - didn't like it - "0x200 too long" used eepromtool_04 to immo off - seemed to work used me7eeprom to write... made it to verify and failed on verify error 0x70101 Sooo... I'm approx.... here.. with this post now... lol http://nefariousmotorsports.com/forum/index.php?topic=1168.msg49183#msg49183 Title: Re: me7.1.1 boot mode ok - normal cant connect for DTC readout Post by: bkwrzdub on March 08, 2022, 08:00:15 AM Code: C:\Users\user\Desktop\manual audiv8fbinfile>ME7EEPROM -p 4 -b 10400 --bootmode 9 it looks like the first tool pulled off a dump with an invalid checksum? and then was immo off'd and checksum corrected.. just wont verify write? thanks Title: Re: me7.1.1 boot mode ok - normal cant connect for DTC readout Post by: bkwrzdub on March 08, 2022, 09:18:22 AM http://nefariousmotorsports.com/forum/index.php?topic=1168.555
That thread references the write verify error 0x70101 as a "bug" I did read out my EEPROM with what I had intended to write and in does indeed match with the IMMO OFF'd file created thru argdub's tool as read thru hexeditor! but eepromtool says the following Code: C:\Users\user\Desktop\manual audiv8fbinfile>eepromtool_04 miamiverify.bin I had then attempted to read thru nefmoto and specify memory layout... no dice I'll keep updated Title: Re: me7.1.1 boot mode ok - normal cant connect for DTC readout Post by: bkwrzdub on March 08, 2022, 07:40:05 PM well
my 4d0907560CL seems to be bricked... (again?) cant seem to get a proper/original eeprom loaded onto the 95P08 :( and the 560 J box seems to function and communicate, IMMO Off seems to have taken despite the verification failure 0x70101 BUT in nefmoto the CL box did seem to write a flash, but that's where the problems began the J box says memory layout is incorrect, and wouldnt take a OBD flash from nefmoto. says "Request upload from ECU failed, ECU reports service is not supported. Request upload may have been disabled by aftermarket engine software." so I'm kinda lost... nah... I'm totally lost. Title: Re: me7.1.1 boot mode ok - normal cant connect for DTC readout Post by: bkwrzdub on March 10, 2022, 06:52:49 AM Dear diary ....
or... To whom it may concern... lmfao So there's some successes and failures here... One ecu - one I got off ebay from miami way... 4e0907560(J) 2005 Audi D3 A8 ....BFM? powers up does go bootmode I do have EEPROM dump, and I did IMMO OFF using Argdub's tool and put the EEPROM bin back on... but when trying to read or write flash in nefmoto... it doesn't like the memory layout, and fails with RequestUpload disabled / Aftermarket software? warning. But it does power up and lists a 4.2... but if it were aftermkt tune, dimes to donutholes it'd be tuned for auto - that's a safe presumption? So... that's the one ECU the original ECU I had from before in my collection was 4D0907560CL came from a c5 a6 4.2... 200? 1? it did manage to boot and connect I think I flashed the EEPROM wrong? and the FLASH Successful??? I did manage to read the flash in nefmoto, then write the manual file to it... but then it wont boot? doesnt connect? it always fails ME7EEPROM/ME7gui-cmdlets on verifying writes with error 0x70101... which, in the other thread is ?knownbug? (I had tried 95040 & 95p08 chipsettings) argdubs tool did manage to chksum OK prior to loading I cant load flash thru galletto (coz EEPROM incorrect?) Galletto also says "ECU NUMBER NOT FOUND" when bootmode read - but wont write - fails on ERASE. I cant seem to load the ori EEPROM read BACK ON the CL unit... so bricked unless I can desolder the 95p08 and burn it for the proper bosch HW & SW #'s? annnnnnnd annnnyways.. in other news I did come across https://nefariousmotorsports.com/forum/index.php?topic=3088.0 that post - which talks of Hex editing either a FTDI cable... OR hex editing the galletto exe.... I was successful in that! (HEXing the EXE file) So no more switching cables!! baby steps.... Title: Re: me7.1.1 boot mode ok - normal cant connect for DTC readout Post by: BlackT on March 10, 2022, 07:12:24 AM You can't write 4.2 ECU tru OBD(cheap tools) only boot mode galleto 1260
Title: Re: me7.1.1 boot mode ok - normal cant connect for DTC readout Post by: bkwrzdub on March 12, 2022, 02:08:48 AM You can't write 4.2 ECU tru OBD(cheap tools) only boot mode galleto 1260 No, I understand that - and that's not what I was attempting read out thru obd immo off and checksum write back thru bootmode eeprom will "write" but fail with 0x70101 unit is bricked - can read out EEPROM in bootmode, will not accept EEPROM or FLASH Title: Re: me7.1.1 boot mode ok - normal cant connect for DTC readout Post by: bkwrzdub on March 13, 2022, 06:09:57 AM I believe the flash memory chip AM29F800BB... is bad
when it's read out thru galletto, it looks as if it's got part of an eeprom bin file..... then it repeats parts of the galletto program prompts and warnings? and it wont erase to write flash... presumeably coz it's got the wrong software on it? I'll look into picking up another unit or two and giving this another shot new post soon Thanks BlackT! Thanks all! |