Go to file
PK Chan 9f9e00a62d net: mqtt: Added event for MQTT ping response.
There are scenarios where there is a NAT firewall in between MQTT
client and server. In such case, the NAT TCP timeout may be shorter
than MQTT keepalive timeout and TCP timeout. The the MQTT ping
request message is dropped by the NAT firewall, so that it cannot be
received by the server, resulting in void MQTT ping response message.
There is no TCP FIN or RST at all. The application looks hang-up
until TCP timeout happens on the client side, which may take too
long.

Therefore, the event MQTT_EVT_PINGRESP is added to inform the
application that the route between client and server is still valid.

Signed-off-by: PK Chan <pak.kee.chan@nordicsemi.no>
2020-03-12 11:07:14 +02:00
.github ci: support license check with topic branch with v3 2020-02-20 18:22:58 -06:00
.known-issues doc: add .known-issue regex for struct bt_mesh_model_pub warnings 2019-12-12 12:39:35 -06:00
arch arm: aarch64: Reintroduce _ASM_FILE_PROLOGUE 2020-03-11 09:34:24 +01:00
boards drivers: uart: miv: convert to DT_INST defines 2020-03-11 16:37:22 -06:00
cmake scripts: Dynamically add driver subsystems to subsystems list 2020-03-11 17:13:39 +02:00
doc doc: keep IDs when redirecting URLs 2020-03-11 08:46:26 -04:00
drivers timer: mchp_xec_rtos: convert to use DT_INST_ defines 2020-03-11 21:16:16 -04:00
dts dts: mec1501hsz: add GIRQ fields for RTOS timer 2020-03-11 21:16:16 -04:00
ext global: Remove leading/trailing blank lines in files 2019-12-11 19:17:27 +01:00
include net: mqtt: Added event for MQTT ping response. 2020-03-12 11:07:14 +02:00
kernel kernel: Add static threads to k_thread_foreach functions 2020-03-12 10:48:29 +02:00
lib pthread: add setname/getname glibc extensions 2020-03-10 15:15:34 +02:00
misc
modules modules: mbedtls: Better help for MBEDTLS_BUILTIN vs MBEDTLS_LIBRARY 2020-03-10 15:10:15 +02:00
samples samples: display: lvgl use posix input, remove defaults 2020-03-11 13:23:19 -05:00
scripts scripts: Replace hard-coded subsystem list with __subsystem annotations. 2020-03-11 17:13:39 +02:00
soc drivers: uart: miv: convert to DT_INST defines 2020-03-11 16:37:22 -06:00
subsys net: mqtt: Added event for MQTT ping response. 2020-03-12 11:07:14 +02:00
tests tests: drivers: gpio_basic_api: silence coverity warning 2020-03-11 16:22:57 -04:00
.checkpatch.conf checkpatch: suppress mailback option in conf file 2020-02-06 08:31:53 -05:00
.clang-format
.codecov.yml
.editorconfig editorconfig: Set max_line_length to 80 2020-02-27 12:57:23 +02:00
.gitattributes
.gitignore docs: guide: Add build system information 2019-11-15 14:58:51 -05:00
.gitlint
.mailmap mailmap: add entry for Sean Nyekjaer 2019-11-04 14:33:31 +01:00
.shippable.yml ci: Bump to SDK 0.11.2 and CI image 0.11.4 2020-02-14 20:54:33 +02:00
.uncrustify.cfg
CMakeLists.txt scripts: Dynamically add driver subsystems to subsystems list 2020-03-11 17:13:39 +02:00
CODE_OF_CONDUCT.md
CODEOWNERS codeowners: add subsys/dfu codeowner 2020-03-10 15:04:46 +02:00
CONTRIBUTING.rst
Kconfig kconfig: Clean up header comments and make them consistent 2019-11-04 17:31:27 -05:00
Kconfig.zephyr doc: update BOOTLOADER_MCUBOOT description 2020-02-19 07:30:43 -06:00
LICENSE
Makefile
README.rst global: Remove leading/trailing blank lines in files 2019-12-11 19:17:27 +01:00
VERSION release: post release patch level = 99 2020-03-10 11:57:47 +02:00
version.h.in
west.yml mgmt: Added Kconfig values and west.yml changes for mcumgr new version 2020-03-11 10:11:31 +01:00
zephyr-env.cmd
zephyr-env.sh zephyr_env.sh: Remove semicolons at ends of lines 2019-12-10 14:34:46 -08:00

.. raw:: html

   <a href="https://www.zephyrproject.org">
     <p align="center">
       <img src="doc/images/Zephyr-Project.png">
     </p>
   </a>

   <a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
   src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>
   <img
   src="https://api.shippable.com/projects/58ffb2b8baa5e307002e1d79/badge?branch=master">


The Zephyr Project is a scalable real-time operating system (RTOS) supporting
multiple hardware architectures, optimized for resource constrained devices,
and built with security in mind.

The Zephyr OS is based on a small-footprint kernel designed for use on
resource-constrained systems: from simple embedded environmental sensors and
LED wearables to sophisticated smart watches and IoT wireless gateways.

The Zephyr kernel supports multiple architectures, including ARM Cortex-M,
Intel x86, ARC, Nios II, Tensilica Xtensa, and RISC-V, and a large number of
`supported boards`_.

.. below included in doc/introduction/introduction.rst

.. start_include_here

Getting Started
***************

Welcome to Zephyr! See the `Introduction to Zephyr`_ for a high-level overview,
and the documentation's `Getting Started Guide`_ to start developing.

Community Support
*****************

Community support is provided via mailing lists and Slack; see the Resources
below for details.

.. _project-resources:

Resources
*********

Here's a quick summary of resources to help you find your way around:

* **Help**: `Asking for Help Tips`_
* **Documentation**: http://docs.zephyrproject.org (`Getting Started Guide`_)
* **Source Code**: https://github.com/zephyrproject-rtos/zephyr is the main
  repository; https://elixir.bootlin.com/zephyr/latest/source contains a
  searchable index
* **Releases**: https://zephyrproject.org/developers/#downloads
* **Samples and example code**: see `Sample and Demo Code Examples`_
* **Mailing Lists**: users@lists.zephyrproject.org and
  devel@lists.zephyrproject.org are the main user and developer mailing lists,
  respectively. You can join the developer's list and search its archives at
  `Zephyr Development mailing list`_. The other `Zephyr mailing list
  subgroups`_ have their own archives and sign-up pages.
* **Nightly CI Build Status**: https://lists.zephyrproject.org/g/builds
  The builds@lists.zephyrproject.org mailing list archives the CI
  (shippable) nightly build results.
* **Chat**: Zephyr's Slack workspace is https://zephyrproject.slack.com.  Use
  this `Slack Invite`_ to register.
* **Contributing**: see the `Contribution Guide`_
* **Wiki**: `Zephyr GitHub wiki`_
* **Issues**: https://github.com/zephyrproject-rtos/zephyr/issues
* **Security Issues**: Email vulnerabilities@zephyrproject.org to report
  security issues; also see our `Security`_ documentation. Security issues are
  tracked separately at https://zephyrprojectsec.atlassian.net.
* **Zephyr Project Website**: https://zephyrproject.org

.. _Slack Invite: https://tinyurl.com/y5glwylp
.. _supported boards: http://docs.zephyrproject.org/latest/boards/index.html
.. _Zephyr Documentation: http://docs.zephyrproject.org
.. _Introduction to Zephyr: http://docs.zephyrproject.org/latest/introduction/index.html
.. _Getting Started Guide: http://docs.zephyrproject.org/latest/getting_started/index.html
.. _Contribution Guide: http://docs.zephyrproject.org/latest/contribute/index.html
.. _Zephyr GitHub wiki: https://github.com/zephyrproject-rtos/zephyr/wiki
.. _Zephyr Development mailing list: https://lists.zephyrproject.org/g/devel
.. _Zephyr mailing list subgroups: https://lists.zephyrproject.org/g/main/subgroups
.. _Sample and Demo Code Examples: http://docs.zephyrproject.org/latest/samples/index.html
.. _Security: http://docs.zephyrproject.org/latest/security/index.html
.. _Asking for Help Tips: https://docs.zephyrproject.org/latest/guides/getting-help.html