[Mshumacher]

Hello I need please Flash+eeprom of same car.
( Or at least eeprom, that i suppose is damaged, but would be better to have complete flash+eeprom incase need to be matched)
Mazda 5 2.0 Liter 110hp
Diesel
Hardware RF8K18881
Software SW-RF8KEK000.HEX

The history of this car is, it had dpf light on, they tried a "tested method" to reset dpf light without diagnostic device, that consisted on connecting a cable from dpf sensor to the negative of the car battery, but they connected it by mistake to the positive terminal of the car battery, made a short circuit.... Car didnt start anymore. On dash light with car lock immo. ( Maybe they damaged the ecu physically, or maybe only software)

I had a look at the dtcs on the ecu at the car
P0602-00 PCM Programming Error
P0602-FF PCM Programming Error
P1260-FF Theft Attempt, vehicle immobiliser engaged
P1675-00 Inyector data not programmed
P1675-FF Inyector data not programmed

Tried with diagnostic to match pcm with immo, it stayed forever on establishing communication, i even left it 25min.. nothing.

With the ecu on bench, i connected ForScan extended license ( No i dont have VCM with IDS but its on my need to buy list), to try to load pcm calibration file downloaded with the VIN number, *.ab file but it gave error when trying to load the file. If trying to push the button load as factory data it said error couldnt find VIN number. I also didnt find option to edit VIN number, Or initialize pcm ? (Maybe it could initialize pats system PCM in the car because it will need to connect to the dash) (Im new to Forscan) ?

Anyway about the calibration pcm block, it looked apparently ok ?


So i suspect the eeprom must be corrupted, what eeprom should it have 93CXX ??

I was able to read the flash file with mpps.

Anyway i think it would be best to flash a good eeprom+flash pack , and after that if the error p0602 is gone, try to match it to the car from that point? Or maybe someone has good virgin eeprom ?? I attach files flash.bin and the ab pcm files...