zephyr/samples/net/zoap_server
Marcus Shawcroft 954baea90b random: Restructure RANDOM Kconfig
Restructure the RANDOM Kconfig to match the structure used in other
drivers with a single top level menu.  Move the true random number
generators to appear first in the menu, with pseudo generators at the
bottom.  Do not present pseudo generators if a true random generator
is presented.

This change implies that tests, samples and applications that require
the random driver interface must now select CONFIG_RANDOM_GENERATOR.

In order for tests and samples to build (and run) on platforms that
have no random driver it remains necessary to select
the CONFIG_TEST_RANDOM_GENERATOR.

Note that CONFIG_TEST_RANDOM_GENERATOR retains its original purpose of
enabling a random driver that delivers non random numbers for the
purpose of testing only.

Change-Id: I2e28e44b4adf800e64a885aefe36a52da8aa455a
Signed-off-by: Marcus Shawcroft <marcus.shawcroft@arm.com>
2016-12-13 22:50:18 +00:00
..
src samples/zoap_server: Fix wrong reference count 2016-12-02 12:40:58 +02:00
Makefile samples/zoap_server: Using unified kernel API 2016-12-02 12:41:12 +02:00
README.txt samples/zoap-server: Add a README.txt to zoap-server 2016-10-01 01:11:27 +00:00
prj.conf random: Restructure RANDOM Kconfig 2016-12-13 22:50:18 +00:00
testcase.ini

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

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