This is an automated email from the ASF dual-hosted git repository. xiaoxiang781216 pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/nuttx.git
commit 1f261d5991dfff69a2fd1db0a2121a222a27fcfb Author: dechao_gong <[email protected]> AuthorDate: Wed Oct 14 18:23:42 2026 +0800 Documentation/rtl8730e: document the watchdog Add the Features bullet and the wdg config section for the on-chip watchdog on rtl8730e_evb: WDG4, the CA32 non-secure system watchdog, at /dev/watchdog0. Record that it has no board wiring and cannot be stopped by software once enabled (stop() instead arms the early interrupt and refreshes the counter from its handler). Assisted-by: Claude <[email protected]> Signed-off-by: dechao_gong <[email protected]> --- .../platforms/arm/rtl8730e/boards/rtl8730e_evb/index.rst | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/Documentation/platforms/arm/rtl8730e/boards/rtl8730e_evb/index.rst b/Documentation/platforms/arm/rtl8730e/boards/rtl8730e_evb/index.rst index a9d724a47ed..3f42b623bdd 100644 --- a/Documentation/platforms/arm/rtl8730e/boards/rtl8730e_evb/index.rst +++ b/Documentation/platforms/arm/rtl8730e/boards/rtl8730e_evb/index.rst @@ -46,6 +46,7 @@ Supported in this NuttX port: the SDK fwlib timer layer * General-purpose timers exposed as ``/dev/timerN`` character devices, with microsecond timeouts and a periodic expiration callback +* On-chip watchdog exposed as a ``/dev/watchdog0`` character device * littlefs persistent storage mounted at ``/data`` (a dedicated SPI NOR flash partition), backing the Wi-Fi key-value store * Wi-Fi station and SoftAP through the ``wapi`` tool @@ -175,6 +176,20 @@ with the example:: nsh> timer # 20 samples 0.1 s apart, 1 s timeout, on /dev/timer0 +wdg +--- + +Minimal NSH with the watchdog driver and the ``wdog`` example (no Wi-Fi). +The board registers the on-chip watchdog at ``/dev/watchdog0`` (see +``boards/arm/rtl8730e/rtl8730e_evb/src/rtl8730e_wdg.c``): WDG4, the CA32 +non-secure system watchdog. It has no board wiring (it is an internal +timer) and, once enabled, cannot be stopped by software -- the stop() +operation instead arms the early-interrupt and refreshes the counter from +its handler to inhibit the reset. Exercise it with the example, which +opens the device, sets a timeout, and pings it:: + + nsh> wdog # run the watchdog example on /dev/watchdog0 + Wi-Fi =====
