zephyr/samples/net/zoap_server
Benjamin Walsh 8cf56bcac7 unified: dissociate system workqueue from common workqueue module
Making a reference to the common work queue code should not necessarily
drag in the system workqueue, since it is possible to use a workqueue
that is not the system workqueue. This is done by moving the system
workqueue into its own code module.

Moving the system workqueue to its own code module allows removing the
NANO_WORKQUEUE and SYSTEM_WORKQUEUE kconfig options, and compiling the
common workqueue code and system workqueue all the time. They are only
linked in the final image if a reference to them exist, same as the
other kernel modules.

Change-Id: I6f48d2542bda24f4702e7c2e317818dd082b3c11
Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2016-11-04 22:39:54 +00:00
..
src samples/zoap_server: Add preliminary support for validation 2016-10-17 02:12:12 +00:00
Makefile samples: tests: remove obsolete KERNEL_TYPE and kernel variables 2016-11-04 15:47:25 -04:00
README.txt samples/zoap-server: Add a README.txt to zoap-server 2016-10-01 01:11:27 +00:00
prj.conf unified: dissociate system workqueue from common workqueue module 2016-11-04 22:39:54 +00:00
prj.mdef
testcase.ini samples: zoap server: exclude quark d2000 not enough ram 2016-09-14 21:23:25 +00:00

README.txt

Title: CoAP Server

Description:

A simple CoAP server showing how to expose a simple resource.

This demo assumes that the platform of choice has networking support,
some adjustments to the configuration may be needed.

The sample will listen for requests in the CoAP UDP port (5683) in the
site-local IPv6 multicast address reserved for CoAP nodes.

The exported resource, with path '/test', will just respond any GET to
that path with the the type, code and message identification retrieved
from the request. The response will have this format:

Type: <type>
Code: <code>
MID: <message id>

--------------------------------------------------------------------------------

Building and Running Project:

This project has no output in case of success, the correct
functionality can be verified by using some external tool like tcpdump
or wireshark.

See the net-tools[1] project for more details

It can be built and executed on QEMU as follows:

    make qemu

[1] net-tools:
    https://gerrit.zephyrproject.org/r/gitweb?p=net-tools.git;a=tree

--------------------------------------------------------------------------------

Troubleshooting:

Problems caused by out-dated project information can be addressed by
issuing one of the following commands then rebuilding the project:

    make clean          # discard results of previous builds
                        # but keep existing configuration info
or
    make pristine       # discard results of previous builds
                        # and restore pre-defined configuration info

-------------------------------------------------------------------------------