PDA

View Full Version : 9s12xdp384 xprog problem reading flash



evisdaci
24th October, 2018, 06:49 AM
Hello everyone
I have problem during reading Motorola 9S12XDP384 (1L15Y) flash. When i read Eeprom everything is OK, but when i try to read flash i have a problem. Memory of MCU in BDM is 384 KB but when i read it with xprog memory is 2 MB. So is so different memory and different reading from correct dump. So how can i read this MCU in correct way, with memory 384KB. Anybody have experience with this problem and anyone can help to solve this problem

voltechcar
24th October, 2018, 07:47 AM
this is normal..... check what variants file you have when he safe file than you understand because your file have 2.0mb.

evisdaci
24th October, 2018, 10:03 AM
I have save in BIN format. I have see some guys that have read this MCU they have 384 KB memory or 256 KB memory but no 2 MB. It is impossible.

Brat
24th October, 2018, 11:07 AM
This is normal,xprog always make flash file 2,048kb,if you try to read xdp512 you will get 2,048kb file not 512kb.
other programmer like vvdi prog make same flash size like write in mcu.

evisdaci
24th October, 2018, 04:05 PM
Ok, but this is not correct because when i write again this dump file the ECU damaget. I have seen some others that have read and the memory is 384 KB or 512 KB

Brat
24th October, 2018, 06:00 PM
You write correct,but maybe you write coruptet dump,wath ecu you want programming?

evisdaci
24th October, 2018, 10:08 PM
Now i want to programming mercedes w204 front sam. I have problem with this ecu. Car not communicate with any ecu. So CGW module have corrupt dump file. Some other people here who have this problem have post flash dump and eeprom dump for this type of MCU and their dump is 384 KB (MC9S12XDP384) and eeprom 4 KB. My eprom is Ok but flash no. One guy's who want to help me to repair my dump said your flash dump is BAD READING. So have any solution how can i read this MCU with xprog in correct way

Zmann
25th October, 2018, 06:27 AM
If you understand one feature of MC9S family that supports dynamic memory allocation, Xprog manages that feature by presetting maximum data size of 2048 KB as template.

Look the read data closely by HEX editor in the 2048 KB file you will see !

evisdaci
25th October, 2018, 09:08 PM
Zmann thank you for your replay, but can u explain me more about this because i didn't understand good. So with Xprog have any chance to read 384 KB memory ? How other person here have read 384 KB memory from this MCU

Zmann
26th October, 2018, 12:43 PM
When a 9S12 has been implemented by users (ECU manufacturer programmer), they have some flexibility to write their program data in some different addresses on the flash to suit their need. The whole program data may divided into some separation and not necessary being in one consecutive area but my image is too simplified as only one. This is possible by dynamic flash feature of these MCU's.

Xprog, when reading these flexible devices, uses big enough memory template of 2048 KB to ensure that no parts of the data was missed.

Now you understand that in the read file of 2048 KB there is content of only 384 KB. Hope you understand my English.

evisdaci
28th October, 2018, 12:45 AM
Thank you for your help, i want to ask you if have any way to read with Xprog only the 384 KB memory from this MCU ? Unused data i don't want so i need only this 384 KB, have any way. Thanks

morgano
28th October, 2018, 09:22 AM
Mate, Zmann explanation is very clear, i never worked with that mcus, but is clear that your 384kb data is inside the 2mb file, just need to open wlth hexeditor and find the offset, then cut the rounding FFFFFFFFs and you get you clean content. Upload your 2mb reading to have a look.

evisdaci
28th October, 2018, 09:26 AM
Here is my flash. So i need only used 384 KB to repair my dump because i need to write flash on my CGW module for mercedes W204

morgano
28th October, 2018, 04:54 PM
Seems the data is there, but is spread along the whole file in little blocks like a bomb exploded there.

pipina
28th October, 2018, 08:38 PM
Hi, just use the same tool to read and write and all will be OK. Member Zmann explains you good, I make you a few examples don't try to use it because I don't know if is at correct address start and end. But the principle is that.

Regards

evisdaci
28th October, 2018, 09:29 PM
Thank you all of you friends, not i use hexeditor and get the 384 KB flash by 2048 KB. I select all the rows that are explained in Xprog manual. Below are my flash and eprom for my CGW module. Anyone can help to repair my dump.

pocinas
29th October, 2018, 12:51 AM
Have simmular problems with xprog and 9s256.... finnaly bought ORANGE 5 and where mcu read 256kb when xprog 2mb file

evisdaci
29th October, 2018, 12:54 AM
Orange 5 clone from china ? It work fine ?

galaxy0634
29th October, 2018, 02:04 AM
Upa clone is the best for reading

pocinas
29th October, 2018, 02:17 PM
Orange 5 clone from china ? It work fine ?Yes i used Orange 5 clone to read and write MC9S12H256 Without problem. But if i know UPA is good as well.

What i like in orange 5 if example i wrote wrong flash every time chip was detected anyway.

With Xprog 5.5.5 chip after wrong file write was not detected....off course i wake up bootloder and chip was again detected but need use pcb adater and solder 2 another wires plus desolder quartz..

Look maybe as well Vvdi prog 4.7.3 is cost much more but i think ...think.support more devices