Linux timer issue
The issue with a Linux timer on AM5726 device running for over 388 days is explained through deep analysis, revealing the system counter's behavior and its impact on device response. The root cause lies in the system counter not updating due to the coarse counter reaching its limit. This results in the system becoming unresponsive. By examining the AM5726 datasheet and understanding the counter frequencies, the timer duration can be converted and the issue can be resolved by managing the counter transitions effectively.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
SDK version: ti-processor-sdk-linux-rt-am57xx-evm-02.00.02.11 The device will no response after runing 388day 3 hours and 18 minutes. And use ssh can access the device, use uptime like below:
Deep analysis: Am5726 system counter is 48bit and will not update after full. We have use jtag tool to read the register twice, the second one read 1 minutes after first one. REG_CTXA15_CP15_C14_CNTVCT_64B always 0xBB8000000000.
Check am5726 datasheet , when extern crystal is 20MHZ the system counter frequency is 6147541HZ . So we convert 0xBB8000000000 the timer is 33535104s(388 days 3 hours and 18.72 minutes). The SOC have 2 independent timer counter: 40Bit coarse counter, frequency 32KHZ, full time the 388.138days. 48Bit system counter, frequency 6.14MHZ, full timer 527.7days. When coarse counter full and turn to 0, the system counter always no change, this cause the issue.
