Dear Quectel Support Team,
I am working on an EC200-based LTE01R03A08_C_SDK_U , I am trying to implement watchdog using ql_dev_cfg_wdt and ql_dev_feed_wdt ,When watchdog is not fed I am not observing any reset.
How can I successfully Reset?
Thank you for your support.
Dear @Roopa ,
Thank you for reaching out.
On EC200 QuecOpen, ql_dev_cfg_wdt() only takes effect if the watchdog is successfully enabled and configured to perform a system reset on timeout. If the watchdog is not resetting, it means either (1) the watchdog is not actually enabled/started, (2) it is still being fed by another task/timer in the project, (3) the timeout/mode is not configured as a reset action, or (4) the watchdog feature is disabled in the current SDK build.
To validate and fix this conclusively, please run a controlled test: configure the watchdog with a short timeout (e.g., 5 seconds) and confirm ql_dev_cfg_wdt() returns success, then intentionally do not call ql_dev_feed_wdt() and block the CPU in a tight loop. If the watchdog is enabled and configured for reset, the module must reset within the timeout. If it does not reset, then the watchdog is not active in your current firmware/SDK build or it is being fed elsewhere.
Please share (1) your exact ql_dev_cfg_wdt() parameters (timeout/mode), (2) the return values from ql_dev_cfg_wdt() and ql_dev_feed_wdt(), and (3) confirm whether any other task in your code calls ql_dev_feed_wdt(). With these three items we can pinpoint which of the above conditions is blocking the reset and provide the exact correction for your project.
Best Regards,
Aghelan