Chuck, I have reviewed the data sheets as you suggested and continued with a bit of data collection on my own. The data sheet indicates for my conditions that Bank 7 should erase in typically 14mS, but up to a max of 100mS. Under extreme conditions, which my product may experience, it could take up to 8 seconds. My system is running at 200MHz. Based on that, the TI_Fee_MainFunction() typical returns in about 3.3uS if it is in idle state. When I fill an entire sector and wrap over to the next sector the same function returns in just over 4mS. This has become problematic for me. My main RTOS system runs with a cycle of 2.5mS and must be deterministic in its cycle time. Failure to complete a cycle in under that time frame faults the system. I cannot predict when the TI_Fee_MainFunction() will complete in 3.3uS vs the 4mS so I cannot even prepare for the extended FEE cycle by overriding RTOS fault settings for that cycle. I'm not sure what the FEE driver is doing in that 4mS. If there is a way to break that up into smaller chunks so I can limit the FEE cycle time to smaller intervals that would solve my problem, but I do not see anything in the FEE user guide that suggests how that could be done. Is there a way to specify the maximum time limit for the TI_Fee_MainFunction()? I'm kind of stuck between a 2.5mS rock and a 4mS hard place. Any suggestions would be appreciated. Thanks, Allen
↧