net/unicoap: Unified and Modular CoAP Stack: Resource Observation (pt 4)

examples/networking/coap/unicoap_client/Makefile

@@ -0,0 +1,78 @@
+# Default Makefile, for simple unicoap server sample application
+
+# name of your application
+APPLICATION = unicoap_client
+
+# If no BOARD is found in the environment, use this default:
+BOARD ?= native
+
+# This has to be the absolute path to the RIOT base directory:
+RIOTBASE ?= $(CURDIR)/../../../..
+
+# Include packages that pull up and auto-init the link layer.
+# NOTE: 6LoWPAN will be included if IEEE802.15.4 devices are present
+USEMODULE += netdev_default
+
+# use GNRC by default
+LWIP_IPV4 ?= 0
+LWIP_IPV6 ?= 0
+
+ifeq (,$(filter 1, $(LWIP_IPV4) $(LWIP_IPV6)))
+  USEMODULE += auto_init_gnrc_netif
+  # Specify the mandatory networking modules
+  USEMODULE += gnrc_ipv6_default
+  # Additional networking modules that can be dropped if not needed
+  USEMODULE += gnrc_icmpv6_echo
+else
+  ifeq (1,$(LWIP_IPV4))
+    USEMODULE += ipv4_addr
+
+    USEMODULE += lwip_arp
+    USEMODULE += lwip_ipv4
+    USEMODULE += lwip_dhcp_auto
+    CFLAGS += -DETHARP_SUPPORT_STATIC_ENTRIES=1
+  endif
+
+  ifeq (1,$(LWIP_IPV6))
+    USEMODULE += ipv6_addr
+
+    USEMODULE += lwip_ipv6
+    USEMODULE += lwip_ipv6_autoconfig
+  endif
+endif
+
+# Import unicoap
+USEMODULE += unicoap
+
+# Import client submodule
+USEMODULE += unicoap_client
+# URI support
+USEMODULE += unicoap_client_uri
+
+# Observation support
+USEMODULE += unicoap_observation
+
+# This module is needed for CoAP over UDP
+USEMODULE += unicoap_driver_udp
+
+# This module is needed for CoAP over DTLS
+USEMODULE += unicoap_driver_dtls
+
+# Use object dump to print response payload in hex
+USEMODULE += od
+
+# Use shell module to accept and parse RIOT shell commands to send requests with configurable
+# CoAP request methods.
+USEMODULE += shell
+
+# It is okay to import only either of the CoAP over UDP and CoAP over DTLS drivers.
+
+# Comment this out to disable code in RIOT that does safety checking
+# which is not needed in a production environment but helps in the
+# development process:
+DEVELHELP ?= 1
+
+# Change this to 0 show compiler invocation lines by default:
+QUIET ?= 1
+
+include $(RIOTBASE)/Makefile.include

examples/networking/coap/unicoap_client/README.md

@@ -0,0 +1,30 @@
+# Sample Client Application With `unicoap`
+
+This a sample application demonstrating how you send CoAP requests using `unicoap`,
+the unified and modular CoAP suite in RIOT. Visit the
+[`unicoap` client tutorial on doc.riot-os.org](http://doc.riot-os.org/group__net__unicoap__client__tutorial.html)
+for a detailed code-level instructions.
+
+## Running the Example on RIOT's Native Board
+
+Create a tap interface (to which RIOT will connect):
+
+```sh
+sudo ip tuntap add tap0 mode tap user ${USER}
+sudo ip link set tap0 up
+```
+
+To try this example on your host, run:
+```sh
+BOARD=native make flash term
+```
+This will compile and run the application.
+The application will print a network-layer address.
+
+In a second terminal session, you can run
+
+```sh
+python3 server.py"
+```
+
+to send a CoAP request through the tap interface to the CoAP server.

examples/networking/coap/unicoap_client/app.config

@@ -0,0 +1,14 @@
+# This is a lighter version of debug logging where only API misuse, missing modules, and
+# tips to fix these issues are logged, without trace logs.
+CONFIG_UNICOAP_ASSIST=y
+
+# This is the full version of debug logging, including trace logs. When this is enabled,
+# the previously mentioned API misuse, missing modules, and fix-its will also be diagnosed.
+# So when you enable debug logging, you do not need to set CONFIG_UNICOAP_ASSIST.
+CONFIG_UNICOAP_DEBUG_LOGGING=n
+
+CONFIG_UNICOAP_CREATE_THREAD=y
+
+CONFIG_UNICOAP_CLIENT_CANCELLABLE=y
+
+CONFIG_UNICOAP_DEBUG_LOGGING=y