***LONG OVER DUE UPDATE***
It's now widely accepted the correct way to repair the FRM3 is by reading dflash.
Once you have a good dump you can extract the good eeprom dump by using this tool:
http://tlvps.tomvanleeuwen.nl/frm/
Offline:
https://github.com/tomvleeuwen/dflas...leases/tag/1.1
All credit to @tomvanleeuwen
https://www.bimmerpost.com/forums/sh...php?p=22126642
***END OF UPDATE***
I get many PM's regarding bricked FRM3 repair. So thought this thread could be a point of information for people who want to repair their bricked module. By bricked I means EEPROM damage through coding / programming due to voltage fluctuation resulting in IFH-0009 error and no communication via OBD.
In this case the module is still good but requires a good EEPROM dump / p-flash being written to it. Once the good EEPROM is in, communication via obd should be restored and vin / VO will need to changed. You also need to find a correct zusb number and flash it with winkfp.
INFO:
MCU is a 9S12XDT384 (mask 3M25J)
DATASHEET -
http://cache.freescale.com/files/mic...S12XDFAMPP.pdf
PROGRAMMERS confirmed to support this MCU:
UPA USB Programmer
XPROG-M
R270
ORANGE
EEPROM DUMPS:
My collection of FRM3 dumps - p-flash and EEPROM.
https://drive.google.com/open?id=0B0...nprQzI3R1N2aFE
METHOD:
Basically...
1. Erase EEPROM (4096bytes)
2. Write good dump
3. Verify obd working and change vin / VO as if retrofitting used FRM3.
4. Flash with correct zusb number for your vehicle using winkfp.
To connect to the MCU there are 3 methods I'm aware of:
1. In socket - desolder chip
2. In circuit - BDM points - reverse of PCB - see image attached.
3. Direct - test clips onto pins like Pamona Micro Grabbers or cheaper alternative.
Connections to:
BKGD
RESET
VDDR (5v)
VSS
Hopefully this is helpful for someone.