Motorola 912 9S12 Programmer ETL problem

[alfons37]

I have buy Motorola 912 9S12 Programmer ETL and work project on mc9s12 dg128b (0L85d) (project is volvo v70 2004 DIM)
I solder NEW mcu direct to board with programmer, i erase eeprom/flash and write to mcu.
And all work 100% with write and verify, but when i read mcu i have 2048 kB on flash and i read eeprom and it have 2048kb, what is wrong :)
Epprom shall have 2 kb NOT 2048kb

Anyone have advice for this ETL programmer and this mcu?

Thanks

[Zmann]

That due to HC912's memory characteristic the programmer makers need to make their stuff to suit them, by creating a fixed larger size memory template. So you need to know the area of the memory you want to save (start-end addresses, normally with high light) and set it in the save criteria.

[alfons37]

But how do I set the addresses in the ETL?

[alfons37]

Now i set 0X0000-0X7FF in etl program, and now it give 2 kb in eeprom but when i write and read i see only FFFF in all file

[Zmann]

Look at 'device' selection window to determine what area of eeprom to be saved, for DG128 eeprom will be put in $800 - $FFF. In save window selects save as BIN too.

edit: for 9S12 DG128B eep is at $4800 - $4FFF

[alfons37]

My new mcu is MC9S12DG128BCPV, i order from china.
Shall i use this edit: for 9S12 DG128B eep is at $4800 - $4FFF and save BIN file. And is it only options for eeprom, so i dont need touch anything when i work with flash?

Here is picture, i am beginner on ETL :)

[Zmann]

Now I think I know your goal, to clone the MCU? so you may not need to pay attention on where of each memory range. Open the device MC9S12DG128B. Select read both by pressing the two buttons, EEPROM and FLASH then Start. Both of the memory will be read into the same template and better to save the whole data with option 'ETL Extended format' (for backup).

To program the new MCU, in Program sequence button press only Programm EEPROM and FLASH (suggest to verify it later if need) then start.

With the new MCU it may not need to PRESS ERASE and doing so on ETL912 may cause some trickly/risky. Advisable to make comprehensive on the manual especially on the section 5.2 MC9S12 Devices

[alfons37]

I try first program eeprom/flash without press erase button, when i try it say "Programming flash error", after this i press erase and now work with program eeprom/flash, flash work good , i can read and all file is ok, but when i try program eeprom it all ok and i can read file, but file is 2048kb,eeprom shall use 2kb.Have you teamviewer, maybe you can help me? :)

[alfons37]

I give up :(, i try without erase and program eeprom/flash (with new MCU), and both eeprom and flash is 2048kb with same information data :(

It cost me 100 usd in mcu now

[Zmann]

Read the latest all data (eep + flash) on the new MCU (EEF format) and post then I am able to check.

Teamviewer may not be an effective tool at this moment because I will need time to find the cause first and possibily by looking at the file.

[alfons37]

Here is 2 files, it is files from DIM cluster from volvo v70 2002 i write to new mcu without erase mcu,
it is eeprom 2kb and flash 2048kb but now i take EFF format when i read this file on new mcu

[Zmann]

I can't find a significant abnormallity on your flash file except the two, significant flash content looks quite small but that can be I think because it's a cluster dump. And the flash security byte is enable but that should not be a concern because you're doing it as ETL OBP. Anyway you can try the followings to disable it and see if helpful

1. On the new MCU delete it thoroughly

2. Read back both eep + flash
- check that all the data were completely deleted (may be done by verfify buttons)
- look at $7BF0F if it has FE (look carefully!) if not...do it (program flash)

3. Thought that you've had a good original data backup in EEF but if you can... newly reread it and leave that on the buffer

4. Put the new chip on... program it and test (may not be convenience if having only one adapter board ? :) )
273175

[alfons37]

The files I put in from another volvo v70, and it is bin size on eeprom and flash files,
maybe better to spend time on xprog and make it work,
do not quite understand what you mean that I should do now. :)

[Zmann]

All the MCU configurations are at some bytes on user memory area. What I look on your file is to check for them and not to your data.
Yes, agree that you try with xprog.

edit: by your current MCU status if as per the above file You will need Xprog on secured mode unless you follow my post above to unsecure it first.

[alfons37]

Now i try with xprog and all work with read and write,verify. I have my customers volvo 2002 volvo v70 DIM and think swap DIM from another car 2004. I read with xprog from DIM 2002 3K91D mask eeprom/flash. Now i take new mcu (mask 0l85d) and solder in DIM 2004 and first take erase all/change security state/clear mcy security. And now i write eeprom with (DIM 2002 3K91D mask eeprom/flash) and after i take flash. I read eeprom/flash and use bin compare all is OK, no problem.
I think now work this DIM in volvo 2002, but NO. Only engine flash yellow. I check soldering, allis ok. What is problem? I did wrong when I removed the safety on MCU?

I can think that many people use old mcu , but has anyone used a new mcu and programmed with xprog or other programmers?

[alfons37]

Anyone?

Anyone write new mcu to volvo DIM?