Part Number: AM623
Hi TI Team,
We are using SDK_11_01_05_03 on our custom board. Due to a recent hardware revision, we removed the external 32.768 kHz crystal and plan to fall back on the internal RC oscillator (LFOSC).
However, after this hardware change, we observed that RESETSTATZ consistently triggers a system reset every 90 seconds after booting.
We would like to ask for your support on the following questions:
1. 90-Second Reset Issue (RESETSTATZ)
-
What is the root cause of
RESETSTATZasserting low every ~90 seconds after removing the 32.768 kHz crystal? (e.g., RTI Watchdog timeout, ESM trigger, or missing clock source in systemd/kernel?) -
How should we reconfigure the clock tree to resolve this reboot loop?
2. Side Effects & Clock Accuracy
-
System Timers (
date,time,sleep,delay): Since the internal LFOSC accuracy is around $\pm1\%$ to $\pm3\%$, will this drift directly affect Linux system time and software timer functions (e.g.,sleep(),usleep(),delay(), or high-resolution timers)? -
External RTC Synchronization: If we use an external RTC (RX8010) and synchronize the Linux system time via
hwclock/ NTP every 5 minutes, will short-term timer calculations and system elapsed time still be noticeably impacted between sync intervals? -
Besides losing deep sleep capability, are there any other potential side effects or degraded features we should be aware of?
3. Required Software Configuration Changes (SDK 11.01.05.03)
-
What specific device tree (DTS) or kernel/U-Boot configs need to be updated in SDK 11.01.05.03 to properly switch from the external 32.768 kHz oscillator to the internal LFOSC clock source?
Thank you for your help and guidance!
Daniel
