zephyr/samples/net/test_15_4
Tomasz Bursztyka 73d8c7c443 net: drivers: cc2520 ieee802154 drivers select relevant options
If no IP stack is seleceted, selecting one of the 2 cc2520 driver will
automatically select the relevant stack.

Change-Id: Icca22da190dc790ce6d302e14c45732f902e02ae
Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-12-02 12:40:24 +02:00
..
src samples: net: fix a memcmp len error 2016-11-18 00:20:12 +00:00
Makefile samples: tests: remove obsolete KERNEL_TYPE and kernel variables 2016-11-04 15:47:25 -04:00
Makefile.15_4
README
prj.conf net: drivers: cc2520 ieee802154 drivers select relevant options 2016-12-02 12:40:24 +02:00
prj.mdef
sample.tc boards: remove obsolete board basic_minuteia 2016-09-22 22:09:34 +00:00
testcase.ini boards: rename Quark SE Devboard to Quark SE C1000 2016-09-16 03:10:31 +00:00

README

802.15.4 test Application:

1) Loopback in single qemu:

    $ make qemu0

 This enables the dummy driver will feed sending 802.15.4 frames back to
 15_4 Rx FIFO. 15_4 Rx FIFO will asseble all frames and feed it to IP Rx FIFO.


2) Loopback between two qemus without monitoring support:

    $ make qemu1

 Then in second window start the other qemu

    $ make qemu2

 If you want to run test 3) then you need to remove the pipes before
 doing so.

    $ make remove_pipes

3) Loopback between two qemus with monitoring support:

    $ make qemu1monitor

 Then in second window start the monitor (found in net/ip/tools directory)
    $ ./monitor_15_4 sample.pcap

 Then in third window start the other qemu

    $ make qemu2monitor

 If you want to run test 2) then you need to remove the pipes before
 doing so.

    $ make remove_pipes



Expert and more detailed instructions:
--------------------------------------
You can execute the tests manually if needed. Just follow the instructions
below.

802.15.4 test Application:

 1) Loopback in single qemu:
 Enable CONFIG_NETWORKING_WITH_15_4_LOOPBACK config option in prj_x86/arm.conf
 to test 802.15.4. By enabling this option dummy driver will feed sending
 802.15.4 frames back to 15_4 Rx FIFO. 15_4 Rx FIFO will asseble all frames
 and feed it to IP Rx FIFO.

 2) Loopback between two qemus:
 Enable CONFIG_NETWORKING_WITH_15_4_LOOPBACK_UART config option in
 prj_x86/arm.conf to send 802.15.4 frames out through QEMU UART and receive
 frames through QEMU UART.

 Follow below simple steps to create fifos at host.

 $ mkfifo /tmp/ip-15-4-1.{in,out}
 $ ln /tmp/ip-15-4-1.in /tmp/ip-15-4-2.out
 $ ln /tmp/ip-15-4-1.out /tmp/ip-15-4-2.in

 Open two terminals and run two qemus with below options.
 $ make qemu QEMU_NUM=1 CONFIG_NETWORKING_WITH_15_4_LOOPBACK_UART=y
 $ make qemu QEMU_NUM=2 CONFIG_NETWORKING_WITH_15_4_LOOPBACK_UART=y

 3) Loopback between two qemus and pcap support:
 Enable CONFIG_NETWORKING_WITH_15_4_LOOPBACK_UART config option in
 prj_x86/arm.conf to send 802.15.4 frames out through QEMU UART and receive
 frames through QEMU UART.

 Follow below simple steps to create fifos at host.

 $ mkfifo /tmp/ip-15-4-1.{in,out}
 $ mkfifo /tmp/ip-15-4-2.{in,out}

 also read net/ip/contiki/tools/README and run monitor_15.4
 and then

 $ make qemu QEMU_NUM=1 CONFIG_NETWORKING_WITH_15_4_LOOPBACK_UART=y
 $ make qemu QEMU_NUM=2 CONFIG_NETWORKING_WITH_15_4_LOOPBACK_UART=y