Try to use newer version like v1251 or v1255 your using older sw
I read a 28F800F3T flash EEPROM from a BMW ME9.2 DME. ECU has MPC555 processor.
Read was successful using BDM100. I virginized the dump using BMW Immo ID Editor. I then tried to write the new dump using BDM100.
I get a "block erasing error". Please see attached photo of CDM screen shot of error.
Is there some step I missed in writing to this flash memory?
Try to use newer version like v1251 or v1255 your using older sw
Kess v2 FW 5.017 full unlimited token - Ktag 7.020 full unlimited token
ALL EDC17/MED17 EEPROM CHECKSUM + VAG IMMO OFF BY EEPROM - NO SAFE
EDC16/17 POPCORN - ME7/7.5 ANTI LAG - LAUNCH ALS/NLS
DPF EGR DTC SCR, Custom Tuning, Damos Translation, FRF / SGO Files
Professional Engine Software Development
Thanks. Will download a new version of CMD today and give it a shot. Will report back if it sorts it out.
Got v1255 and tried it. Same result. Please see attached screen shot.
If I try some other dumps, it writes partially then I get the same block erasing error.
However, if I use the original dump and write it back, it writes successfully without errors.
Could this be related to checksums?
make erase flash first and write new data... will be ok
Thanks for the tip. This means I have to use some other reader/writer since BDM100 does not have erase function (using CMD software).
I have Xprog-M (which has erase function) but am having trouble getting it to read a Bosch ME9.2 DME (BMW). I followed wiring diagrams shown in DK but no luck. Got success only in reading the DME thru BDM100.
One thing I did not do and have not tried is to put power 12v thru the DME external socket pins. Seems the 28F800F3T chip is write protected. BDM100 with CMD sw can read it but won't write on it.
if you can read flash without external power on ecu plug, it is flash receive power, so R/W is same
i have also same trouble when i want write eeprom, i can just write ORI no MOD, i don't know why !
i already check size file and extension name, but always same trouble
yeah you need external power ...
@Peko
Yes, I get the same thing, can write ori but mod file write gives block erase error. Hence, I kind of think there is a
write protect in the flash memory/eeprom. Read the 28f800f3t intel datasheet and it says block write/erase is protected and protection is turned off if VPP > VPPlk. Made me think that external power is needed to do a write.
@Balimotor
Will give this Xprog-M connection diagram you gave. Thanks. Will post results.
One other thing I tried is to use WINOLS to do checksum correction on the modified dump file. Got the same error when I write this checksum corrected file via BDM.
i'm not sure, but i think you burn ecu if you connect external power AND power from BDM to board
because you send 2 power on board, you understand ?
Did not get any success reading using Xprog-M.
Did some tests using BDM100. What I have seen by comparing what I wrote and what I read afterwards from the flash memory is... it is able to write on most of the blocks but in the last block, it is unable to erase. It seems that part is write protected.
Attached is a screen shot of the results using a virginized dump for a DME9.2 flash memory which i tried writing using BDM100.
You will see it is able to write on some blocks but when it reaches a certain block, it fails to erase.
It seems it always fails to erase when something is changed in the last few blocks of the flash. I tried writing different dumps from a 28f800f3t flash.
i have same trouble writing on eeprom 95320 for exemple, and this eeprom isn't secured
so trouble is from BDM software i think
Finally got this sorted out. The flash memory had some blocks which were locked for writing.
Found a thread where it says to short some parts in the circuit board of the ME9.2 to enable write.
Bookmarks