MC9S12XEP100MAL Dflash

[ltx]

Hello

Currently, I'm facing a problem. I have already sought help in the community before. Let me describe the background.
1. We are the manufacturer. Our R&D partner has terminated the cooperation with us. Currently, we only have the bin file.
2. I used the Xeltek programmer (a commercial programmer) to burn the bin file into the microcontroller. The program on the chip can run normally, but the parameters within the program cannot be modified. After modification, they will be reset upon power-off.
3. According to the reply from the community technicians, I didn't partition the D Flash. I made a slight modification to the XEP100 - Initial data in Emulated EEPROM - CW47 sample program (changed FCLKDIV = 0x13; the crystal oscillator of my circuit board is 20 MHz) and burned it in the partition. However, the program stopped working. Here are my detailed steps:
Step 1: Erase the chip
Step 2: Use CodeWarrior and BDM to burn the modified XEP100 - Initial data in Emulated EEPROM - CW47 program with the changed crystal oscillator
Step 3: Use the Xeltek programmer (a commercial programmer) to burn the program (1024KB P flash program)
Step 4: The test failed.

May I ask what the current issue is? I sincerely request the community technicians to provide an answer. Thank you very much.

[lukaszadrapa]

Hi @ltx 

Everything depends on your application. It’s very difficult to propose anything without knowing exactly how the application works, how it handles data, and how it uses the EEPROM partition. I don’t think we can suggest a solution without further details. We have no problem assisting with the MCU itself, but we cannot provide support for your application — especially since you only have it as a binary file, not as a project.

Regards,

Lukas

[ltx]

hi   lukaszadrapa

 Thank you very much for your reply. I would like to know a few more issues that you can help me solve.
Can this chip be partitioned first and then have the bin program burned onto it? Is the burning process I described in the previous question correct?

[lukaszadrapa]

Yes, you can use this approach, I can see no problem here. The s-record or binary file just should not contain data in area which is reserved for EEE backup memory. 

[ltx]

Thank you very much for your reply. But I'm sorry to say that I still have some questions to trouble you with.
Does your reply, "The s-record or binary file just should not contain data in area which is reserved for EEE backup memory," mean that I cannot write data to the completed D flash partition during the burning process?
After I completed the partition program burning, when I used the commercial burner "Blank check", it showed that the chip memory was not empty. After the partition configuration is completed, will data be stored in P FLASH and D FLASH?

[lukaszadrapa · Accepted solution]

On S12XEP100, you can program D‑Flash during burning, but do not place any bytes into the EEE backup area created by the partition. Only write to the user D‑Flash region.

After you run the Partition D-Flash command, the device pre-programs EEE metadata pages in D‑Flash. So a “Blank check” will report non‑blank—that’s normal.

To know exactly which addresses you must avoid in your S‑record, read the EEE configuration after partitioning. You can use either EEPROM Emulation Query command or you can read DFPART and ERPART fields directly  in IFR at global address 0x12_0000. This IFR is hidden by default, you need to enable the visibility by EEEIFRON in MMCCTL1 register. Just search for “EEEIFRON” in the manual for details.

You can also take a look at EEE.xls file in this package:

https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/16-bit/14941/1/EEPROM-XEP100-Example+des...

Partitioning does not affect P-Flash, you can program P-Flash as usual.