NefMoto > Noob Zone > Noob Questions (Moderator: turboat) > me7.1.1 boot mode ok - normal cant connect for DTC readout
Pages: [1]
« previous next »
Author Topic: me7.1.1 boot mode ok - normal cant connect for DTC readout  (Read 3158 times)
bkwrzdub
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11
« 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
1037363442

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
1037352378

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!
« Last Edit: February 26, 2022, 01:42:18 PM by bkwrzdub » Logged
bkwrzdub
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11
« Reply #1 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
« Last Edit: March 07, 2022, 08:14:24 PM by bkwrzdub » Logged
BlackT
Hero Member
*****

Karma: +79/-40
Offline Offline

Posts: 1425
« Reply #2 on: March 07, 2022, 11:45:00 PM »
Read eeprom as 95040, immo off that file, do chc, write it as 95040
Logged
bkwrzdub
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11
« Reply #3 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!
« Last Edit: March 08, 2022, 07:06:49 AM by bkwrzdub » Logged
bkwrzdub
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11
« Reply #4 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
« Last Edit: March 08, 2022, 07:35:51 AM by bkwrzdub » Logged
bkwrzdub
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11
« Reply #5 on: March 08, 2022, 08:00:15 AM »
Code:
C:\Users\user\Desktop\manual audiv8fbinfile>ME7EEPROM -p 4 -b 10400 --bootmode 9
5040 --CSpin P6.3 -r miami3.bin
ME7_EEPROM v1.40
COM: 4, Baud Rate: 10400
Memory type: 95040, size: 512
Chip Select pin: P6.3
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xD5 ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Reading IDCHIP ... 0x0C44: C167CS ... OK
Initializing registers ... OK
Sending EEPROM driver ... OK
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Reading EEPROM ... OK
File saved
Closing COM4

C:\Users\user\Desktop\manual audiv8fbinfile>eepromtool_04 miami3.bin
Read in 512bytes
EEPROM Status:
- Type: ECU_eeprom
- Version: Immo3
- VIN: WAUML44E75N015835 (Audi 2005 - A8 2003 on, Neckarsulm, Germany; Mlada Bol
eslav)
- SKC: 034684
- Immobiliser: On
- Checksum: Invalid Checksum
- Size: 512bytes
- Cluster Code: 30 8D 22 F0 61 1A 45
- P0601 DTC: not set
- Immo ID: AUX3Z0E1760106
- Softcoding ID: 7773
- Tuner Tag:
- Flash Programming (successful): 0
- Flash Programming (attempts): 0


C:\Users\user\Desktop\manual audiv8fbinfile>ME7Check miami3.bin
ME7Check: binary file miami3.bin has not correct length (is 0x200 bytes long, 0x
80000 or 0x100000 bytes expected)

C:\Users\user\Desktop\manual audiv8fbinfile>eepromtool_04 --in miami3.bin --out
miami3_off.bin --immo off
Read in 512bytes
Setting Immobiliser: Off
- Immobiliser Off
- Setting backup pages
- Correcting checksums

- Write Successful


C:\Users\user\Desktop\manual audiv8fbinfile>eepromtool_04 miami3_off.bin
Read in 512bytes
EEPROM Status:
- Type: ECU_eeprom
- Version: Immo3
- VIN: WAUML44E75N015835 (Audi 2005 - A8 2003 on, Neckarsulm, Germany; Mlada Bol
eslav)
- SKC: 034684
- Immobiliser: Off
- Checksum: OK
- Size: 512bytes
- Cluster Code: 30 8D 22 F0 61 1A 45
- P0601 DTC: not set
- Immo ID: AUX3Z0E1760106
- Softcoding ID: 7773
- Tuner Tag:
- Flash Programming (successful): 0
- Flash Programming (attempts): 0

C:\Users\user\Desktop\manual audiv8fbinfile>ME7EEPROM -p 4 -b 10400 --bootmode 9
5040 --CSpin P6.3 -w miami3_off.bin
ME7_EEPROM v1.40
COM: 4, Baud Rate: 10400
Memory type: 95040, size: 512
Chip Select pin: P6.3
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xD5 ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Reading IDCHIP ... 0x0C44: C167CS ... OK
Initializing registers ... OK
Sending EEPROM driver ... OK
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Writing EEPROM ................................ OK
Verifying EEPROM write ... FAIL. (error=0x70101)
Closing COM4


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
« Last Edit: March 08, 2022, 08:15:36 AM by bkwrzdub » Logged
bkwrzdub
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11
« Reply #6 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
Read in 1024bytes
Found 1024b bin - parsing as a R32 bin - experimental
ERROR: 1024byte file detected, but the last 512bytes are not all padded with 0xF
F, this file is may be a corupt dump, a cluster dump or something other than an
eeprom dump, open it with a hex editor - if this is a valid eeprom please post t
he file and vehicle info on the thread for this tool
EEPROM Status:
- Type: ECU_eeprom
- Version: Immo3
- VIN: WAUML44E75N015835 (Audi 2005 - A8 2003 on, Neckarsulm, Germany; Mlada Bol
eslav)
- SKC: 034684
- Immobiliser: Off
- Checksum: Invalid Checksum
- Size: 1024bytes - 512bytes expected, check this is a eeprom bin
- Cluster Code: 30 8D 22 F0 61 1A 45
- P0601 DTC: not set
- Immo ID: AUX3Z0E1760106
- Softcoding ID: 7773
- Tuner Tag:
- Flash Programming (successful): 0
- Flash Programming (attempts): 0


I had then attempted to read thru nefmoto and specify memory layout...

no dice

I'll keep updated
« Last Edit: March 08, 2022, 09:34:37 AM by bkwrzdub » Logged
bkwrzdub
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11
« Reply #7 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

Sad

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.
« Last Edit: March 09, 2022, 06:06:50 AM by bkwrzdub » Logged
bkwrzdub
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11
« Reply #8 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....
« Last Edit: March 10, 2022, 06:57:37 AM by bkwrzdub » Logged
BlackT
Hero Member
*****

Karma: +79/-40
Offline Offline

Posts: 1425
« Reply #9 on: March 10, 2022, 07:12:24 AM »
You can't write 4.2 ECU tru OBD(cheap tools) only boot mode galleto 1260
Logged
bkwrzdub
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11
« Reply #10 on: March 12, 2022, 02:08:48 AM »
Quote from: 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


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
Logged
bkwrzdub
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 11
« Reply #11 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!
Logged
Pages: [1]
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • November 30, 2024, 03:54:57 AM
  • Welcome, Guest. Please login or register.
    Did you miss your activation email?

    Login with username, password and session length
Search
 
Advanced Search
About Disclaimer
All Rights Reserved 2010 Nefarious Motosports
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.022 seconds with 16 queries. (Pretty URLs adds 0.001s, 0q)