mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-29 04:50:03 +01:00
429de92251
19346: pkg/tinydtls: allow build for AVR r=benpicco a=benpicco 19512: SUBSYSTEMS.md: add jia200x to subsystems r=benpicco a=jia200x 19513: boards/nrf52840dongle/doc: Update nrfutil pointers r=benpicco a=chrysn ### Contribution description Nordic changed its nrfutil; this change adjust to it. I'm not fully happy with recommending that tool at all due to its bad quality (see rambling in https://github.com/RIOT-OS/RIOT/issues/19511), but short of soldering on a debug header or touch-probing it with wires it's the only way in to the device. I may later add follow-up recommendations to switch to riotboot, but this now at least fixes the immediate issue. ### Testing procedure * Look at the updated documentation. ### Issues/PRs references Closes: https://github.com/RIOT-OS/RIOT/issues/19511 19514: dist/testbed-support: remove obsolete boards from iotlab archi r=benpicco a=aabadie Co-authored-by: Benjamin Valentin <benjamin.valentin@ml-pa.com> Co-authored-by: Benjamin Valentin <benjamin.valentin@bht-berlin.de> Co-authored-by: Jose Alamos <jose@alamos.cc> Co-authored-by: chrysn <chrysn@fsfe.org> Co-authored-by: Alexandre Abadie <alexandre.abadie@inria.fr> |
||
|---|---|---|
| .. | ||
| dtls-client.c | ||
| dtls-server.c | ||
| main.c | ||
| Makefile | ||
| Makefile.ci | ||
| README.md | ||
| tinydtls_common.h | ||
| tinydtls_keys.h | ||
DTLS sock async test application
This is a test application for DTLS sock sock_dtls_t with sock_async.
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 += -DCONFIG_DTLS_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.