Hello everyone! At present, the API of C40_ip component is used for the DFlash erase operation in the project. However, I found from the manual that the DFlash and PFlash of S32K314 have a lifespan of only 1000 cycles for sector erase. So I am eager to know how to use NXP approved EEEPROM drivers.
And most importantly, all the components used in this project belong to 'Drivers', not' MCAL '. I would like to know what solutions are currently available to increase the lifespan requirements for DFlaser erase and write cycles in the project.
Looking forward to receiving a response from the community.
Solution for your issue is to use our EEPROM emulation drivers that are part of RTD driver package (FEE driver).
Thank you very much for your reply!
At present, I can only find the FEE component in the "MCAL" component, but all existing projects are developed based on the "Driver" component, mainly due to this contradiction.
Thank you very much for your answer!
I successfully found this demo in the IDE, and I would like to know if the components of "MCAL" and "Driver" can be mixed together?
If possible, is it feasible to use the three fee components from "MCAL" instead of the "C40_ip" component in "Driver" as shown in the demo? Will there be compatibility issues?
Curent RTD version is 6.0.0.
Example and used drivers are following:
Thank you for your reply！
So to use the functionality of EEEPROM, is it currently recommended to fully use the "MCAL" component for implementation? For projects that have already developed most of the functionality and fully use the "Driver" component, the workload of porting is a bit heavy.....
It is not recommended, you could choose one of these layers.
I think it is basically up to you. Fee component will run above flash sections as defined so you can possibly use other section with IP layer, but it is up to you to guarantee coherency.