riot-ci/RIOT
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
RIOT/examples/dtls-sock
History
Jean Pierre Dudey de50518146
cc26x2_cc13x2: use correct RAM value 
Previous value was 20 K, now it's 80 K. The older family of these MCUs
(cc13x0, cc26x0) had that size, currently for cc13x2 and cc26x2 it's
80 K.

Signed-off-by: Jean Pierre Dudey <jeandudey@hotmail.com>
2020-02-10 18:38:15 -05:00
..
dtls-client.c
examples: add DTLS sock example application
2019-12-05 14:08:54 +01:00
dtls-server.c
dtls-sock: check msg_try_receive return value
2019-12-09 14:17:09 +01:00
main.c
examples: add DTLS sock example application
2019-12-05 14:08:54 +01:00
Makefile
examples/dtls-sock: remove TINYDTLS_LOG
2020-02-05 06:59:34 +01:00
Makefile.ci
cc26x2_cc13x2: use correct RAM value
2020-02-10 18:38:15 -05:00
README.md
examples: add DTLS sock example application
2019-12-05 14:08:54 +01:00
tinydtls_keys.h
examples: add DTLS sock example application
2019-12-05 14:08:54 +01:00

README.md

DTLS sock example

This example shows how to use DTLS sock sock_dtls_t.

Testing using RIOT native

For testing, we can use two RIOT native RIOT instances. For that first we need to prepare the network interfaces:

$ ./../../dist/tools/tapsetup/tapsetup --create 2

For the server instance:

$ PORT=tap0 make all term
[...]
> dtlss start
ifconfig

For the client:

$ PORT=tap1 make all term
[...]
> dtlsc <server ip address> "DATA to send"

Debug logs

To enable debug logs uncomment CFLAGS += -DDTLS_DEBUG in the Makefile. Tinydtls supports setting the log level. See Makefile for more info.

Configs and constraints

DTLS sock acts as a wrapper for the underlying DTLS stack and as such, the constraints that applies specifically to the stack are also applied here. For tinydtls, please refer to dtls-echo README.