zephyr/samples/net/echo_server
Tomasz Bursztyka 26a4df620f samples/net: Uses CONFIG_NET_APP_IEEE802154_* options relevantly
In order to simplify when 802.15.4 is selected on these samples, let's
setup the device through a common code.

For this to work, RFD is now the default.

Change-Id: I46590864442f77d83f681cc0e854c94344648856
Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2017-03-31 11:24:27 +02:00
..
src samples/net: Uses CONFIG_NET_APP_IEEE802154_* options relevantly 2017-03-31 11:24:27 +02:00
Makefile
README.rst
prj_arduino_101.conf net: Rename Kconfig.samples and its main option for future changes 2017-03-31 11:24:26 +02:00
prj_arduino_101_cc2520.conf samples/net: Uses CONFIG_NET_APP_IEEE802154_* options relevantly 2017-03-31 11:24:27 +02:00
prj_bt.conf net: Rename Kconfig.samples and its main option for future changes 2017-03-31 11:24:26 +02:00
prj_cc2520.conf samples/net: Uses CONFIG_NET_APP_IEEE802154_* options relevantly 2017-03-31 11:24:27 +02:00
prj_frdm_k64f.conf net: Rename Kconfig.samples and its main option for future changes 2017-03-31 11:24:26 +02:00
prj_frdm_k64f_cc2520.conf samples/net: Uses CONFIG_NET_APP_IEEE802154_* options relevantly 2017-03-31 11:24:27 +02:00
prj_frdm_k64f_mcr20a.conf samples/net: Uses CONFIG_NET_APP_IEEE802154_* options relevantly 2017-03-31 11:24:27 +02:00
prj_nrf5.conf samples/net: Uses CONFIG_NET_APP_IEEE802154_* options relevantly 2017-03-31 11:24:27 +02:00
prj_qemu_802154.conf samples/net: Uses CONFIG_NET_APP_IEEE802154_* options relevantly 2017-03-31 11:24:27 +02:00
prj_qemu_cortex_m3.conf net: Rename Kconfig.samples and its main option for future changes 2017-03-31 11:24:26 +02:00
prj_qemu_x86.conf net: Rename Kconfig.samples and its main option for future changes 2017-03-31 11:24:26 +02:00
prj_sam_e70_xplained.conf net: Rename Kconfig.samples and its main option for future changes 2017-03-31 11:24:26 +02:00
testcase.ini

README.rst

Echo Server
###########

Overview
********

The echo-server sample application for Zephyr implements a UDP/TCP server
that complements the echo-client sample application: the echo-server listens
for incoming IPv4 or IPv6 packets (sent by the echo client) and simply sends
them back.

The source code for this sample application can be found at:
:file:`samples/net/echo_server`.

Building and Running
********************

There are multiple ways to use this application. One of the most common
usage scenario is to run echo-server application inside QEMU. This is
described in :ref:`networking with QEMU <networking_with_qemu>`.

There are configuration files for different boards and setups in the
echo-server directory:

- :file:`prj_arduino_101_cc2520.conf`
  Use this for Arduino 101 with external IEEE 802.15.4 cc2520 board.

- :file:`prj_arduino_101.conf`
  Use this for Arduino 101 with external enc28j60 ethernet board.

- :file:`prj_bt.conf`
  Use this for Bluetooth IPSP connectivity.

- :file:`prj_cc2520.conf`
  Use this for devices that have support for IEEE 802.15.4 cc2520 chip.

- :file:`prj_frdm_k64f_cc2520.conf`
  Use this for FRDM-K64F board with external IEEE 802.15.4 cc2520 board.

- :file:`prj_frdm_k64f.conf`
  Use this for FRDM-K64F board with built-in ethernet.

- :file:`prj_frdm_k64f_mcr20a.conf`
  Use this for FRDM-K64F board with IEEE 802.15.4 mcr20a board.

- :file:`prj_qemu_802154.conf`
  Use this when simulating IEEE 802.15.4 network using two QEMU's that
  are connected together.

- :file:`prj_qemu_cortex_m3.conf`
  Use this for ARM QEMU.

- :file:`prj_qemu_x86.conf`
  Use this for x86 QEMU.

- :file:`prj_sam_e70_xplained.conf`
  Use this for Atmel SMART SAM E70 Xplained board with ethernet.

Build echo-server sample application like this:

.. code-block:: console

    $ cd $ZEPHYR_BASE/samples/net/echo_server
    $ make pristine && make CONF_FILE=<your desired conf file> \
      BOARD=<board to use>

Make can select the default configuration file based on the BOARD you've
specified automatically so you might not always need to mention it.

Running echo-client in Linux Host
=================================

There is one useful testing scenario that can be used with Linux host.
Here echo-server is run in QEMU and echo-client is run in Linux host.

Run 'loop_socat' and 'loop-slip-tap' scripts from net-tools in Linux host.

.. code-block:: console

    $ ./loop_socat.sh

In another window:

.. code-block:: console

    $ sudo ./loop-slip-tap.sh

Run echo-server application in QEMU:

.. code-block:: console

    $ cd $ZEPHYR_BASE/samples/net/echo-server
    $ make pristine && make qemu

In third window:

.. code-block:: console

    $ sudo ./echo-client -i tap0 2001:db8::1

Note that echo-server must be running in QEMU before you start the
echo-client application in host terminal window.