NefMoto

Technical => Flashing and Chipping => Topic started by: Ne-FF on April 20, 2015, 09:53:50 AM



Title: Question about bin 018P
Post by: Ne-FF on April 20, 2015, 09:53:50 AM
i have audi a4 b5 ATW engine 018P.
I read it today with nefmoto soft using 800BB, because 400bb did not read my car.

I read on this forum, that my car should have 512 mb file, but nefmoto soft saved 1024 mb file.
Is it right?


Title: Re: Question about bin 018P
Post by: vwaudiguy on April 20, 2015, 12:12:00 PM
i have audi a4 b5 ATW engine 018P.
I read it today with nefmoto soft using 800BB, because 400bb did not read my car.

I read on this forum, that my car should have 512 mb file, but nefmoto soft saved 1024 mb file.
Is it right?

Can you link to where you read this engine code should be 512mb? I believe ATW is 1024mb.


Title: Re: Question about bin 018P
Post by: ddillenger on April 20, 2015, 12:42:35 PM
ATW is 512!

If nefmoto gives an error, "Memory layout appears invalid" whilst using 29F400BB, just ignore it!


Title: Re: Question about bin 018P
Post by: Ne-FF on April 21, 2015, 10:34:34 AM
This is log when i'm trying to read flash with 400BB and 57600 baud

Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: 4B0906018P  1.8L R4/5VT         0006
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Sending start communication request.
Connected
Disabling Windows sleep mode.
Reading ECU flash memory.
ECU reports programming session preconditions have been met.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
ECU reports that security access is not supported.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Validating flash memory starts at 0x00800000 and ends at 0x00880000.
End address is not the end of flash memory.
Reading ECU flash memory failed. Trying to force ECU to recognize read operation is complete.
Finished forcing ECU to recognize that failed read operation is complete.
Reading ECU flash memory failed.
100% complete.
Restoring Windows sleep mode.
Disconnecting...
Disconnected


Title: Re: Question about bin 018P
Post by: TLS on April 22, 2015, 07:31:15 PM
I think you are getting kb confused with mb.

If you downloaded a 1024kb file from your 512kb ecu, just go with it.
Open it in tunerpro and have a look at the HEX. It should be uniform from 512kb onwards.
I think you can use the Bin Splitter to cut off the unused bits.

Have a look at other 512kb bins to see what happens near the end of them. There is at least another 018P file here with a definition that TijnCU used with his 512kb 018AA file and that XDF is here to.

(Hopefully if I am talking garbage Dave will correct me...)