Hello @DavidSHIH
Thanks for contacting us and using the NXP products. Based on your description, your test application code should be from yourself. And then this situation is more likely to be the system task scheduling failure and CLRC 663 crashed with some error status. And with these considerations, here some comments to you and try.
1. Since you are a long-term test, it is recommended that you add exception event prints to your code, such as whether any system task switch error and stay on the same task after running a period of time. And then leads to the system be crashed.
2. In principle, after and before of each polling cycle, need to check CLRC 663 status register to see if there are any abnormal states, and if so clear it to ensure that the thread can continue...
3. Is the one-second polling cycle too short? During polling, maybe need to read/write EEPROM of CLRC663. Therefore, can you increase the polling interval and try?
The above for your reference and hope to help.
To update this case, you may reply by email.
To provide confidential information or attachments, you may add that online.
Please login to our NXP technical support portal:
https://support.nxp.com/s/case/5002p00002s4bZWAAY
The portal allows access to the full details of the case, including the previous communication.
Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.
Best regards,
Kelly
Technical Support
NXP Semiconductor
