When I debug a Example flash_partitioning_s32k144 from SDK and debug configurations as illustrated in following figure.
Then IDE appeared pegdbserve_console.exe has stoped as following picture show.
So, I was tried to fix it by update PEmcrio from Help->install new software->work with PEMicro - http://www.pemicro.com/eclipse/updates. After it installed done, things got worse when I tried to debug again.The GDB Server was not able to establish a connection to the target processor. And Flash an elf file also went wrong.
I'm sure the PE drive and s32k144 EVB is all right. I tried to reinstall S32DS, but again, once you preserve memory and perform a debug , you have a problem. It's fine when you Flash with preserve memory.
Hi @ybb34713,
It seems like there is a bug in the PE Micro plugin.
Please read these two threads:
https://community.nxp.com/t5/S32-Design-Studio/Pe-Micro-preserve-memory-bug/m-p/976739
I think you can just preserve the partitioning.
In the example, the FlexNVM block is used for EEE Backup and it is not accessible anyway - it can be erased by Mass Erase only, and the debugger will not mass erase the MCU if the Preserve Partitioning for the device option is used.
Regards,
Daniel
Hi, @danielmartynek
First of all, thank you for your reply. I've seen the two threads you mentioned before, and they don't seem to solve the problem. I would like to share with you my test results and questions I would like to ask you.
1. Unfortunately, the DFLASH (all backed up as EEPROM) data will still be erased by testing if I just preserve the partitioning.
In the flash algorithm file freescale_s32k144f512m15_pflash_dflash_eeprom.arp, as shown in the figure below, you can see that the Mass Erase directive might have been used, but I'm not sure if it had anything to do with it.
2. Surprisingly, if I just preserve the partitioning and used the Flash algorithm file nxp_s32k144f512m15_sector_erase.arp, the DFLASH data would not be erased. 
3. Another discovery when using nxp_s32k144f512m15_sector_erase.arp is that if you use Non-Volatile Memory Preservation to preserve DFlash, the download program still has errors. I think this is probably the reason why you can only use FlexRAM to access it.
If the PFLASH is preserved (for example, 0x0007f000-0x0007ffff), it performs fine, downloads the program successfully and can read the data previously written to the PFLASH.
In conclusion, If we can solve the problem with this，I want to confirm whether nxp_s32k144f512m15_sector_erase.arp can be used as freescale_s32k144f512m15_pflash_dflash_eeprom.arp ：
1.) Is nxp_s32k144f512m15_sector_erase.arp the RTM version?
2.) What is the difference between nxp_s32k144f512m15_sector_erase.arp and freescale_s32k144f512m15_pflash_dflash_eeprom.arp ? Why do you need to provide two Flash algorithms?
Looking forward to your reply.
Best wishes,
Bob
Hi @ybb34713,
If the partitioning has been preserved (this can be verified in the DEPART register), the FlexNVM block is not erased. The FlexVNM block can be erased by Erase All Blocks / Mass erase only if the FlexNVM is partitioned for EEPROM, but this would remove the partitioning too.
So, If EEPROM backup size != 0, the FlexNVM is partitioned for EEPROM and the FlexNVM is not erased.
The EEPROM is then ready (FlexRAM contains valid data) when EEERDY = 1.
Regards,
Daniel
Hi Daniel,
This configuration, provided by you, ensures that FlexNVM(EEPROM) data will not be erased by simply checking Preserve Partitioning for the device and not preserving the memory range of FlexNVM?
Regards,
Bob
