Help¶

Once the TFTP Client sends out a request, it will wait TFTPC_REQUEST_TIMEOUT msecs for the data to arrive from the TFTP Server. However, if it doesn’t arrive within the given time we will re-transmit the request to the server in hopes that the server will respond within time to this request. This number dictates the number of times we will do re-tx of our request before giving up and exiting.

Direct dependencies¶

TFTP_LIB && NETWORKING

(Includes any dependencies from ifs and menus.)

Default¶

5

Kconfig definition¶

At <Zephyr>/subsys/net/lib/tftp/Kconfig:29

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:34 → <Zephyr>/subsys/Kconfig:37 → <Zephyr>/subsys/net/Kconfig:89 → <Zephyr>/subsys/net/lib/Kconfig:12

Menu path: (Top) → Sub Systems and OS Services → Networking → Link layer and IP networking support → Network Protocols → Socket TFTP Library Support [EXPERIMENTAL]

config TFTPC_REQUEST_RETRANSMITS
    int "Number of times the TFTP Client will retransmit the request to the server."
    default 5
    depends on TFTP_LIB && NETWORKING
    help
      Once the TFTP Client sends out a request, it will wait
      TFTPC_REQUEST_TIMEOUT msecs for the data to arrive from the TFTP Server.
      However, if it doesn't arrive within the given time we will re-transmit
      the request to the server in hopes that the server will respond within
      time to this request. This number dictates the number of times we will
      do re-tx of our request before giving up and exiting.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)