Mini R50 dash MC912DG128A problem

[Yhoni]

Hello friends, I have two Mini R50 dash. The one in the car is faulty and the display light does not light up and the km are not displayed, the other one I bought second-hand to fix the display of the first one.
The dash are almost identical aesthetically but they have differences:
The one with the car:
- MC912DG128A (0K50E)
- Hardware 04
- Software 14

The second-hand shopper:
- MC912DG128 (3K91D)
- Hardware 10
- Software 20

I was only going to replace the display driver (ref: PCF8576CH) but I decided to make a backup of the two dash in case there was any problem in replacing the driver.

The problem now is that after reading the two dash with Xprog, eeprom and flash, neither of the two boxes turn on. They are dead.

Could someone tell me what I've done wrong, please?

I attach the reading files.

[Steve182]

You killed both dashes... now you will need a flash to every dash to wake up again.
but you need to check your connection and if it’s posible use another programmer.
i have flash and eeprom exactly hw 10 sw 20 for your sencond hand dash

[Yhoni]

You killed both dashes... now you will need a flash to every dash to wake up again.
but you need to check your connection and if it’s posible use another programmer.
i have flash and eeprom exactly hw 10 sw 20 for your sencond hand dash

Ok Steve182, but what is the reason that the reading has been corrupted? Is there a protocol to read the mic? Could the reason be to read the eeprom first and then the flash or vice versa?

Are the readings that I have done corrupted?

Is there a protocol to write the firmware back?

Is it necessary to re-secure the mic after writing is done?

Could someone clarify these doubts for me, please?

Thanks.

[km666]

Mini dash is very dangerous.
What version X-prog?
Twisted pair lenght 12 cm?
0K50E,and 3K91D not same version in xprog.
Check pdf,and lift pin 47,97.
Post result.

[Yhoni]

Mini dash is very dangerous.
What version X-prog?
Twisted pair lenght 12 cm?
0K50E,and 3K91D not same version in xprog.
Check pdf,and lift pin 47,97.
Post result.

Hello, i used Xprog 6.26 and yesterday i could unlocked and read two dash but now i can´t.

I tiwsted pair today and equal yesterday.

I followed the Xprog instructions to connect each of the mics.

I am trying with 3K91D adn the xprog lights seem to do the reading but it doesn't read anything, I have tried lifting pin 47 on the 3k91d and it does the same.

Could the xprog have killed the 3k91d by doing the read? Is there any way to check it? :concern:

I will try more late the other dash with 0K50E and report.

Thanks.

[Steve182]

Ok Steve182, but what is the reason that the reading has been corrupted? Is there a protocol to read the mic? Could the reason be to read the eeprom first and then the flash or vice versa?

Are the readings that I have done corrupted?

Is there a protocol to write the firmware back?

Is it necessary to re-secure the mic after writing is done?

Could someone clarify these doubts for me, please?

Thanks.

-you've erased the flash... thats why the dash is dead
-no protocol... just a good programmer and good conections (NO NEED TO LIFT ANY PIN)
-no need to resecure

HERE IS A GOOD EEPROM AND GOOD FLASH TO WAKE UP YOUR SECOND HAND DASH.... just write it to your dash...

[Yhoni]

Hello, i could to read eeprom 3K91D again with UPA and i can write too but UPA do not read/write the flash:
Motorola HC12*: MC68HC912B32, MC68HC912BE32, MC68HC912D60, MC68HC912D60A, MC68HC912DC128A, MC68HC912DG128, MC68HC912DG128A
*EEPROM only

i can not read and can not write with Xprog how i did yesterday and i am trying to read flash with Orange5 but i do not know how to connect pinout exactly.

I made a query in this other post:
https://www.digital-kaos.co.uk/forums/showthread.php/894313-Orange5-connection-dude?p=4112980#post4112980

Anyone could help me with Orange5 , please ?.

Thanks.

[km666]

Via orange 5 must be desolder Mcu.
Reflesh Xprog 5.55 ,it work stable.

[Yhoni]

Hello friends, I have regained the connection between the Xprog programmer and the MC68HC912DG128-secure 0K50E and can now read and write it.

Now I am going to open another post requesting the flash and eeprom file for the hard: 04 and the soft: 14 and try to recover it.

The link: https://www.digital-kaos.co.uk/forums/showthread.php/895115-I-need-flash-and-eeprom-for-Mini-R50-dash-hw-04-soft-14

Thanks.

[urgi]

Any chance Flash for MINI

- MC912DG128 (3K91D)
- Hardware 10
- Software 21 or 22

Just wondering why is this MCU so sensitive ???

As well why saving of Flash is only 2048 KB instead @Steve182 128KB :y:

[urgi]

Any chance Flash for MINI

- MC912DG128 (3K91D)
- Hardware 10
- Software 21 or 22

Just wondering why is this MCU so sensitive ???

As well why saving of Flash is only 2048 KB instead @Steve182 128KB :y:

forgot mentioned is for MINI 6211-6957297