I am using the TI_FEE driver in my project to emulate a simple EEPROM to store configuration settings. My system has critical timing functions that must occur in very specific time frames. I can manually time simple read and writes to the EEPROM and get an idea of how long each of these functions takes. My concern come in under a specific condition in the FEE driver. When the data writes fill an entire sector and roll over to the next, the original sector must be erased in preparation for the next roll over of data. A sample run of the FEE_FORMAT function takes 36.4mS on my system and cannot be called asynchronously (i.e. when called it takes fully system resources until completed). I assume the FEE driver must perform a similar function internally to erase the unused sector for the next set of data. My concern is how long will the FEE driver will tie up the system if it needs to erase a memory sector though an internal call of a write cycle.
1. Is there a table that provides maximum clock cycles for each FEE instruction?
2. Is there a maximum time the TI_Fee_MainFunction() will run when called?
3. Can the TI_Fee_MainFunction() be suspended (not called) from the main system indefinitely, or must it be serviced in a specific length of time?
Related, the FEE driver provides a Fapi_serviceWatchdogTimer() user function to handle updating the watchdog during a extended FEE cycle, but no timing details are provided on how often this is called. I do not see where this is called in the FEE driver so it is hard to tell which functions call it and how often.
It seems I has seen a document with this information at one point in time, but now all I can find is the "TI FEE Driver User Guide" which does not provide this detail.
Thanks,
Allen
