:orphan: .. title:: LOG_BACKEND_RTT_RETRY_DELAY_MS .. option:: CONFIG_LOG_BACKEND_RTT_RETRY_DELAY_MS *Delay between TX retries in milliseconds* Type: ``int`` Help ==== Sleep period between TX retry attempts. During RTT session, host pulls data periodically. Period starts from 1-2 milliseconds and can be increased if traffic on RTT increases (also from host to device). In case of heavy traffic data can be lost and it may be necessary to increase delay or number of retries. Direct dependencies =================== \ :option:`LOG_BACKEND_RTT_MODE_BLOCK ` && \ :option:`LOG_BACKEND_RTT ` && !\ :option:`LOG_FRONTEND ` && !\ :option:`LOG_MINIMAL ` && \ :option:`LOG ` *(Includes any dependencies from ifs and menus.)* Default ======= - 5 Kconfig definition ================== .. highlight:: kconfig At ``subsys/logging/Kconfig.backends:113`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:34`` → ``subsys/Kconfig:31`` → ``subsys/logging/Kconfig:25`` Menu path: (Top) → Sub Systems and OS Services → Logging → Backends → Enable Segger J-Link RTT backend .. parsed-literal:: config LOG_BACKEND_RTT_RETRY_DELAY_MS int "Delay between TX retries in milliseconds" default 5 depends on \ :option:`LOG_BACKEND_RTT_MODE_BLOCK ` && \ :option:`LOG_BACKEND_RTT ` && !\ :option:`LOG_FRONTEND ` && !\ :option:`LOG_MINIMAL ` && \ :option:`LOG ` help Sleep period between TX retry attempts. During RTT session, host pulls data periodically. Period starts from 1-2 milliseconds and can be increased if traffic on RTT increases (also from host to device). In case of heavy traffic data can be lost and it may be necessary to increase delay or number of retries. *(The 'depends on' condition includes propagated dependencies from ifs and menus.)*