[Enabled]

Updated from 5,5,1 to 5,5,5. All passed without problems, authorization is all green ...
But with the verification of the problem. I tried on mc9s12xeq384mag 3M25J when erasing it, I specify the entire region (corresponding to d-flash = 0) - the process passes without errors, then I write it to the industry with a few verification errors (errors every time) and when reading the Partition corruption error, I suggest manually selecting partition.
The processor is in the FRM block, 4 points are connected in-circuit. Now I can not understand, or the processor went out of order, or in xprog's case .

This is my exact experience with xprog box 5.5.5. FRM3 MCU signature ID is correctly recognized only 1 out of 10 times, or less.
Does not read/write correctly. There are hundreds of verify errors.

I downgraded to 5.5.1 (bricked 2 atmega64 in the process), and same result.

I upgraded to 5.7.4, and when verifying certificates, it eventually killed my last atmega64 as well. Atmega64 are only $4 USD each, but this clone tool is a nightmare.



I give up. What do you all use for FRM3?

[dil6222]

Updated from 5,5,1 to 5,5,5. All passed without problems, authorization is all green ...
But with the verification of the problem. I tried on mc9s12xeq384mag 3M25J when erasing it, I specify the entire region (corresponding to d-flash = 0) - the process passes without errors, then I write it to the industry with a few verification errors (errors every time) and when reading the Partition corruption error, I suggest manually selecting partition.
The processor is in the FRM block, 4 points are connected in-circuit. Now I can not understand, or the processor went out of order, or in xprog's case .

This is my exact experience with xprog box 5.5.5. FRM3 MCU signature ID is correctly recognized only 1 out of 10 times, or less.
Does not read/write correctly. There are hundreds of verify errors.

I downgraded to 5.5.1 (bricked 2 atmega64 in the process), and same result.

I upgraded to 5.7.4, and when verifying certificates, it eventually killed my last atmega64 as well. Atmega64 are only $4 USD each, but this clone tool is a nightmare.



I give up. What do you all use for FRM3?

Hello enabled your atmegas are not fried just configured incorrectly please check my thread
here https://cartechnology.co.uk/showthread.php?tid=39496 you will be able to.unlock your atmega and reprogram

[Enabled]

Updated from 5,5,1 to 5,5,5. All passed without problems, authorization is all green ...
But with the verification of the problem. I tried on mc9s12xeq384mag 3M25J when erasing it, I specify the entire region (corresponding to d-flash = 0) - the process passes without errors, then I write it to the industry with a few verification errors (errors every time) and when reading the Partition corruption error, I suggest manually selecting partition.
The processor is in the FRM block, 4 points are connected in-circuit. Now I can not understand, or the processor went out of order, or in xprog's case .

This is my exact experience with xprog box 5.5.5. FRM3 MCU signature ID is correctly recognized only 1 out of 10 times, or less.
Does not read/write correctly. There are hundreds of verify errors.

I downgraded to 5.5.1 (bricked 2 atmega64 in the process), and same result.

I upgraded to 5.7.4, and when verifying certificates, it eventually killed my last atmega64 as well. Atmega64 are only $4 USD each, but this clone tool is a nightmare.



I give up. What do you all use for FRM3?

Hello enabled your atmegas are not fried just configured incorrectly please check my thread
here https://cartechnology.co.uk/showthread.php?tid=39496 you will be able to.unlock your atmega and reprogram

I saw that wonderful thread, and have bookmarked it earlier today.
I need to find an oscillator somewhere, and I will recover them. I can try to recover 3 of them.


But I am afraid that the Xprog box still will not work correctly with MC9S12XEQ384.

V5.5.5 was hopeless, and so was the 5.5.1.


   

MCU ID was different 9 out of 10 times.



I am not sure if the 5.7.4 method found online even gets past the certificate verification.

[dil6222]

Updated from 5,5,1 to 5,5,5. All passed without problems, authorization is all green ...
But with the verification of the problem. I tried on mc9s12xeq384mag 3M25J when erasing it, I specify the entire region (corresponding to d-flash = 0) - the process passes without errors, then I write it to the industry with a few verification errors (errors every time) and when reading the Partition corruption error, I suggest manually selecting partition.
The processor is in the FRM block, 4 points are connected in-circuit. Now I can not understand, or the processor went out of order, or in xprog's case .

This is my exact experience with xprog box 5.5.5. FRM3 MCU signature ID is correctly recognized only 1 out of 10 times, or less.
Does not read/write correctly. There are hundreds of verify errors.

I downgraded to 5.5.1 (bricked 2 atmega64 in the process), and same result.

I upgraded to 5.7.4, and when verifying certificates, it eventually killed my last atmega64 as well. Atmega64 are only $4 USD each, but this clone tool is a nightmare.



I give up. What do you all use for FRM3?

Hello enabled your atmegas are not fried just configured incorrectly please check my thread
here https://cartechnology.co.uk/showthread.php?tid=39496 you will be able to.unlock your atmega and reprogram

I saw that wonderful thread, and have bookmarked it earlier today.
I need to find an oscillator somewhere, and I will recover them. I can try to recover 3 of them.


But I am afraid that the Xprog box still will not work correctly with MC9S12XEQ384.

V5.5.5 was hopeless, and so was the 5.5.1.




MCU ID was different 9 out of 10 times.



I am not sure if the 5.7.4 method found online even gets past the certificate verification.

 
Hello it won,t make any difference with reading the chip you want just stops you buying new atmega every time you program     also can use upa for clock signal if you have it 

Also you reading that chip onboard or offboard ?

[Enabled]

I don't have UPA (yet...), but I did just buy an Orange5 to be able to finish these 4 FRMs. No luck at all with my XProg. The china seller claims there's 'nothing wrong' with it, so I lost some money there. :/
Too bad Carprog does not do this MCU.


I am reading the chip onboard with the 4 wires connected on the back:

   


I tried a couple FRMs, and it's always the same. It reads the MC9S12XEQ384 MCU signature ID wrong most of the time, and full of verify errors.
I tried with +12V power to XProg and not. I tried v5.5.1 and v5.5.5.

One day, when I have time, I will recover these 3 Atmega64 I have now, with your instructions.

[dil6222]

I don't have UPA (yet...), but I did just buy an Orange5 to be able to finish these 4 FRMs. No luck at all with my XProg. The china seller claims there's 'nothing wrong' with it, so I lost some money there. :/
Too bad Carprog does not do this MCU.


I am reading the chip onboard with the 4 wires connected on the back:




I tried a couple FRMs, and it's always the same. It reads the MC9S12XEQ384 MCU signature ID wrong most of the time, and full of verify errors.
I tried with +12V power to XProg and not. I tried v5.5.1 and v5.5.5.

One day, when I have time, I will recover these 3 Atmega64 I have now, with your instructions.

Hmm I would try read direct from 9s12 chip legs take a picture of mcu on the board so I can take a look

[Enabled]

Orange5 arrived.

It can read and write BMW FRM MC9S12XEQ384 in circuit just fine.


I noticed that my XPROG writes to the FRM correctly (verified with Orange5), but Xprog cannot read correctly. Any way to fix xprog read?






2nd point.
I see that Orange5 has an oscillator generator capability. How to use this in software? (for the purpose of recovering Atmega64)

[dil6222]

Orange5 arrived.

It can read and write BMW FRM MC9S12XEQ384 in circuit just fine.


I noticed that my XPROG writes to the FRM correctly (verified with Orange5), but Xprog cannot read correctly. Any way to fix xprog read?






2nd point.
I see that Orange5 has an oscillator generator capability. How to use this in software? (for the purpose of recovering Atmega64)

Hello for fixing reading of that 9s12 with xprog I have no idea as I don't have that chip to hand to try reading otherwise I could do some test

As for your orange 5 just use 1000khz /1mhz output other frequencies may work but I haven't tested check your Orange 5 manual for which pin to use as output you only need connect 1 wire from it to xtal1 pin on atmega

[user0086]

Never had any problems with my 5.60 + dongle Xprog, until last week. It now keeps giving (verify) errors.
So I got my spare 5.55 xprog and have all verify errors on all FRM3's like everyone else in this thread.
5.51 works fine with FRM3 but does not recognize the broken partition table of the FRM3.

[Enabled]

Thank you for confirming! I thought I was going nuts with this Xprog... zero help from seller, not that I expected much.

Orange5 is a better tool for FRM, it seems.