zephyr

History

Anas Nashif f62d86c42b samples: get rid of obsolete usage of ARCH variable Using ARCH variable to select different configurations for the different architectures is misleading and conflicts with the variable ARCH being used by the build system. The variable is not needed, it is application specific and an application can be built without the need to specify ARCH on the command line. This is yet another item specific to samples and test cases that wrongfully being used and documented for every application. We need to use another variable and just make it clear it is specific to samples and how they are written. One possible solution is to have a script that gets the architecture based on the board being used. Attachments Jira: ZEP-238 Change-Id: Ieccbc087a41858fb96fb361c0aaa04705e968a4e Signed-off-by: Anas Nashif <anas.nashif@intel.com>		2016-05-12 10:57:28 +00:00
..
Makefile	samples: get rid of obsolete usage of ARCH variable	2016-05-12 10:57:28 +00:00
README	net: Rename samples/network to samples/net	2016-02-05 20:24:39 -05:00
prj.conf	samples: get rid of obsolete usage of ARCH variable	2016-05-12 10:57:28 +00:00
prj.mdef	net: Rename samples/network to samples/net	2016-02-05 20:24:39 -05: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