Read frm3: Xprog 5.55? Xprog 5.84? Orange5 Clone?

Purpose: Read frm3

ECU programmers to try and test reports:

Xprog 5.55 clone reviews on reading FRM3:

1. When I read d-flash is always corrupted. 

2. Had the same with 5.55, no way to verfiy or to read FRM3 correctly.

Bought Xprog 5.84 and no problem anymore.

3. flash the atmega with 5.51 luis andre that is stable, 5.55 is useless.

Orange 5 clone reviews on reading FRM3:

My China Xprog reads differently every read for FRM3. Useless tool, no matter which program version.

I replaced it with Orange5

Orange5 Clone works perfectly fine. The process is very slightly different, but it has been documented here in the forum. It works well 

Clone UPA reviews on reading FRM3:

Clone UPA does not work on frm3 at all.

Downgrade to Xprog 5.51 works but that version lacks the possibility to read broken dflash so you'l have to use a dump from internet and code afterwards.

Enjoy!

www.obd2shop.co.uk

How to fix XPROG can't read MC9S12DG secured?

Question: XPROG (both V5.5 and China clone 6.12) don't read all bytes. It reads only unsecured bytes (pages). I try Windows 7 32 and 64, and Windows XP. The insecurity zone is only FF. 

I think that problem is not in the ECU and connection, but in XPROG and MC9S12 secured MCU, because I read this MCU with VVDI prog without problems.

Post connection and ECU number Or Photo:

Good to know:

Advice: I think the data read by Xprog are OK, sitting at the right memory blocks but the final file size is much bigger than VVDI. 

For example, MC9S12DG256, Flash file has 2 MB of reading by xprog while just 256 if read via VVDI. Someone already compared these two data outputs, please?

+ 1: 

I did once. The size difference is because the Xprog reads the MCU like it was designed by factory. In the window where You choose the MCU family to program, You will see in info, that there are some addresses, that are excluded from memory. 

VVDI Pro and Rosfar read only the memory containing DATA, Xprog reads whole, as well as the blank (FF) spaces between data fragments. 

In Xprog ori software there is a button "Editor Tools" There is an option to convert the files. You can convert the 2MB file to the 256/521 and program with VVDI or Rosfar (it just deletes the FF from blank areas) and vice versa, there is an option to automatically add the blank spaces, and then program file from Rosfar or VVDI by Xprog.

http://blog.obd2shop.co.uk/how-to-fix-xprog-cant-read-mc9s12dg-secured/