Hello
I am using the CRC_calculateFull () function in a lower priority task to cyclically perform a CRC verification to confirm a critical configuration data table that is loaded to flash memory is not corrupted.
The data table is about 80K long, and the application is a real-time critical application.
The intent is this verification process is cyclically performed in the background as a non-real time event, and to ensure the higher priority real time tasks have priority.
I want to ensure I understand the difference between the options Blocking, callback, or polling return behavior.
CRC_RETURN_BEHAVIOR_POLLING : The CPU is used to feed data to the CRC. CRC operation results are available after the function returns.
I do not understand this option.
I am wondering if perhaps I should be using the CRC_addData() and limiting the task to cyclically performing small junks of the CRC calculation and when complete call CRC_finalize()...or can the CRC_calculateFull () function be used with the polling or call back option to support the same desired outcome, which is allowing the higher priority tasks to pre-empt the CRC verification when they are scheduled to run?
Thanks In Advance.
Perry