Home
last modified time | relevance | path

Searched full:tools (Results 1 – 25 of 568) sorted by relevance

12345678910>>...23

/Zephyr-latest/scripts/net/
DREADME.txt2 the network test applications Docker container provided by the 'net-tools'
3 Zephyr project, https://github.com/zephyrproject-rtos/net-tools.
10 'net-tools' Docker container has been created, see the first bullet point
11 at the net-tools Docker README file
12 https://github.com/zephyrproject-rtos/net-tools/blob/master/README.docker.
17 * Check out the net-tools project from github or update it with west
18 * Change working directory to the net-tools repository
20 * Run 'docker build -t net-tools .'
22 This creates a Docker image called 'net-tools' which the script will need as
54 * Docker net-tools image uses addresses 192.0.2.2 and 2001:db8::2
[all …]
Drun-sample-tests.sh5 image=net-tools
6 name=net-tools
39 l="$d/tools/net-tools"
52 echo '$NET_TOOLS_BASE is unset, no net-tools found' >&2
220 docker container exec net-tools $test || return $?
286 $BASENAME [-Z <zephyr base directory>] [-N <net-tools base directory>] [<list of test directories>]
289 network implemented by the 'net-tools' subproject.
293 -N|--net-tools-dir <dir>
294 set net-tools directory
333 -N|--net-tools-dir)
/Zephyr-latest/doc/connectivity/networking/api/
Dppp.rst28 `RFC1661 <https://tools.ietf.org/html/rfc1661>`__)
30 `RFC1662 <https://tools.ietf.org/html/rfc1662>`__)
32 `RFC1332 <https://tools.ietf.org/html/rfc1332>`__)
34 `RFC5072 <https://tools.ietf.org/html/rfc5072>`__)
42 See the `net-tools README`_ file for more details on how to test the Zephyr PPP
45 .. _net-tools README:
46 https://github.com/zephyrproject-rtos/net-tools/blob/master/README.md#ppp-connectivity
Ddns_resolve.rst14 to `IETF RFC1035 on Domain Implementation and Specification <https://tools.ietf.org/html/rfc1035>`_.
23 See `IETF RFC6762 <https://tools.ietf.org/html/rfc6762>`_ for more details
28 See `IETF RFC4795 <https://tools.ietf.org/html/rfc4795>`_ for more details
/Zephyr-latest/
Dwest.yml39 path: tools/bsim/components
46 path: tools/bsim/components/ext_2G4_channel_NtNcable
53 path: tools/bsim/components/ext_2G4_channel_multiatt
60 path: tools/bsim/components/ext_2G4_device_WLAN_actmod
67 path: tools/bsim/components/ext_2G4_device_burst_interferer
74 path: tools/bsim/components/ext_2G4_device_playback
81 path: tools/bsim/components/ext_2G4_libPhyComv1
88 path: tools/bsim/components/ext_2G4_modem_BLE_simple
95 path: tools/bsim/components/ext_2G4_modem_magic
102 path: tools/bsim/components/ext_2G4_phy_v1
[all …]
/Zephyr-latest/samples/net/sockets/echo_server/
Ddocker-test.sh13 start_docker "/net-tools/echo-client -i eth0 192.0.2.1" \
14 "/net-tools/echo-client -i eth0 2001:db8::1" \
15 "/net-tools/echo-client -i eth0 192.0.2.1 -t" \
16 "/net-tools/echo-client -i eth0 2001:db8::1 -t"
/Zephyr-latest/doc/connectivity/networking/
Dnative_sim_setup.rst24 On the Linux Host, find the Zephyr `net-tools`_ project, which can either be
25 found in a Zephyr standard installation under the ``tools/net-tools`` directory
30 git clone https://github.com/zephyrproject-rtos/net-tools
38 * Terminal #1 is terminal window with net-tools being the current
39 directory (``cd net-tools``)
117 Step 2 - run echo-client from net-tools
120 On the Linux Host, find the Zephyr `net-tools`_ project, which can either be
121 found in a Zephyr standard installation under the ``tools/net-tools`` directory
126 git clone https://github.com/zephyrproject-rtos/net-tools
162 .. _`net-tools`: https://github.com/zephyrproject-rtos/net-tools
Dqemu_eth_setup.rst21 On the Linux Host, find the Zephyr `net-tools`_ project, which can either be
22 found in a Zephyr standard installation under the ``tools/net-tools`` directory
27 git clone https://github.com/zephyrproject-rtos/net-tools
35 * Terminal #1 is terminal window with net-tools being the current
36 directory (``cd net-tools``)
90 .. _`net-tools`: https://github.com/zephyrproject-rtos/net-tools
Dnetworking_with_multiple_instances.rst18 On the Linux Host, find the Zephyr `net-tools`_ project, which can either be
19 found in a Zephyr standard installation under the ``tools/net-tools`` directory
24 git clone https://github.com/zephyrproject-rtos/net-tools
31 * Terminal #1 and #2 are terminal windows with net-tools being the current
32 directory (``cd net-tools``)
52 For Zephyr instance #1, create file called ``zephyr1.conf`` to ``net-tools``
71 For Zephyr instance #2, create file called ``zephyr2.conf`` to ``net-tools``
94 The following ``net-setup.sh`` commands should be typed in net-tools
95 directory (``cd net-tools``).
195 .. _`net-tools`: https://github.com/zephyrproject-rtos/net-tools
Doverview.rst25 (`RFC 4862 <https://tools.ietf.org/html/rfc4862>`_).
31 (`RFC 4861 <https://tools.ietf.org/html/rfc4861>`_) is enabled by default.
33 (`RFC 3810 <https://tools.ietf.org/html/rfc3810>`_) is enabled by default.
35 IEEE 802.15.4 networks (`RFC 4944 <https://tools.ietf.org/html/rfc4944>`_).
43 (`RFC 2131 <https://tools.ietf.org/html/rfc2131>`_).
51 (`RFC 768 <https://tools.ietf.org/html/rfc768>`_) is supported.
57 (`RFC 793 <https://tools.ietf.org/html/rfc793>`_) is supported. Both server
75 (`RFC 7252 <https://tools.ietf.org/html/rfc7252>`_) is supported.
95 (`RFC 1035 <https://tools.ietf.org/html/rfc1035>`_) client functionality
100 Both multicast DNS (mDNS) (`RFC 6762 <https://tools.ietf.org/html/rfc6762>`_)
[all …]
Dqemu_setup.rst25 On the Linux Host, find the Zephyr `net-tools`_ project, which can either be
26 found in a Zephyr standard installation under the ``tools/net-tools`` directory
32 git clone https://github.com/zephyrproject-rtos/net-tools
33 cd net-tools
48 * Terminals #2, #3, and #4 are terminal windows with net-tools being the current
49 directory (``cd net-tools``)
96 Now in terminal #4, you can run various tools to communicate with the
253 sudo $ZEPHYR_BASE/../tools/net-tools/tunslip6 -t tapMAIN -T -s /tmp/slip.devMAIN 2001:db8::1/64 &
263 …sudo $ZEPHYR_BASE/../tools/net-tools/tunslip6 -t tapOTHER -T -s /tmp/slip.devOTHER 2001:db8::1/64 &
266 .. _`net-tools`: https://github.com/zephyrproject-rtos/net-tools
/Zephyr-latest/scripts/west_commands/tests/
Dtest_blackmagicprobe.py15 import serial.tools.list_ports
120 @patch('serial.tools.list_ports.comports')
128 fake_comport1 = serial.tools.list_ports_common.ListPortInfo(
131 fake_comport2 = serial.tools.list_ports_common.ListPortInfo(
134 fake_comport3 = serial.tools.list_ports_common.ListPortInfo(
151 @patch('serial.tools.list_ports.comports')
156 fake_comport1 = serial.tools.list_ports_common.ListPortInfo(
159 fake_comport2 = serial.tools.list_ports_common.ListPortInfo(
162 fake_comport3 = serial.tools.list_ports_common.ListPortInfo(
165 fake_comport4 = serial.tools.list_ports_common.ListPortInfo(
[all …]
/Zephyr-latest/samples/net/mqtt_sn_publisher/compose/
Dcompose.yaml8 net-tools:
16 net-tools:
19 net-tools:
/Zephyr-latest/doc/develop/flash_debug/
Dprobes.rst9 the Zephyr application on your host workstation using tools like GDB. They may
12 software supported by Zephyr, see :ref:`flash-debug-host-tools`.
33 that communicate with their respective debug host tools. For example, an
35 with pyOCD or OpenOCD debug host tools, or with J-Link firmware to communicate
36 with J-Link debug host tools.
40 || *Debug Probes & Host Tools* | Host Too…
102 This probe is programmed using the MCU-Link host tools, which are installed
103 with the :ref:`linkserver-debug-host-tools`. NXP recommends using NXP's
104 `MCUXpresso Installer`_ to install the Linkserver tools.
123 This debug probe is compatible with the following debug host tools:
[all …]
Dhost-tools.rst1 .. _flash-debug-host-tools:
3 Flash & Debug Host Tools
6 This guide describes the software tools you can run on your host workstation to
209 .. _linkserver-debug-host-tools:
211 LinkServer Debug Host Tools
217 with custom debug configurations based on GNU tools or as part of a headless solution
222 This method will also install the tools supporting the debug probes below,
223 including NXP's MCU-Link and LPCScrypt tools.
284 .. _jlink-debug-host-tools:
286 J-Link Debug Host Tools
[all …]
/Zephyr-latest/samples/net/dns_resolve/
DREADME.rst62 installation, the sample dnsmasq start script can be found in the `net-tools`_
63 project or downloaded from https://github.com/zephyrproject-rtos/net-tools.
69 $ cd net-tools
85 net-tools uses port 5353 to allow executing the daemon without
102 For testing mDNS, use Avahi script in net-tools project:
106 $ cd net-tools
109 .. _`net-tools`: https://github.com/zephyrproject-rtos/net-tools
/Zephyr-latest/scripts/west_commands/runners/
Dxtensa.py25 parser.add_argument('--xcc-tools', required=True,
26 help='path to XTensa tools')
30 # Override any GDB with the one provided by the XTensa tools.
/Zephyr-latest/samples/net/sockets/packet/
DREADME.rst24 See the `net-tools`_ project for more details.
29 .. _`net-tools`: https://github.com/zephyrproject-rtos/net-tools
/Zephyr-latest/subsys/profiling/
DKconfig6 bool "Profiling tools"
8 Enable profiling tools, such as perf
/Zephyr-latest/doc/develop/getting_started/
Dinstallation_linux.rst20 done so already. While some tools use the environment variables
88 sudo dnf group install "Development Tools" "C Development Tools and Libraries"
127 A :ref:`recent CMake version <install-required-tools>` is required. Check what
189 A :ref:`recent DTC version <install-required-tools>` is required. Check what
197 A :ref:`modern Python 3 version <install-required-tools>` is required. Check
211 Zephyr's supported architectures. It also includes additional host tools, such
283 selection. For example, ``ZEPHYR_SDK_INSTALL_DIR=/company/tools``, where
284 the ``company/tools`` folder contains the following subfolders:
286 * ``/company/tools/zephyr-sdk-0.13.2``
287 * ``/company/tools/zephyr-sdk-a.b.c``
[all …]
/Zephyr-latest/samples/net/sockets/sntp_client/
DREADME.rst25 See the `net-tools`_ project for more details.
30 .. _`net-tools`: https://github.com/zephyrproject-rtos/net-tools
/Zephyr-latest/samples/net/sockets/http_client/
DREADME.rst55 program found in the `net-tools`_ project, enable establishing a secure
63 and run the ``http-server.py`` (from net-tools) on a Linux host.
88 ``https-server.py`` program in net-tools project.
90 .. _`net-tools`: https://github.com/zephyrproject-rtos/net-tools
/Zephyr-latest/tests/net/lib/lwm2m/interop/
DREADME.md16 …Zephyr native network on Linux](https://github.com/zephyrproject-rtos/net-tools/blob/master/README…
19 ### Run Lehan server from net-tools Docker container
21 Zephyr's net-tools Docker container already contains Leshan, so if you don't want to set the enviro…
26 cd tools/net-tools/docker
27 docker build -t net-tools .
32 cd tools/net-tools/
38 …me=net-tools --name=net-tools --ip=192.0.2.2 --ip6=2001:db8::2 -p 8080:8080 -p 8081:8081 -p 5683:5…
39 docker container exec net-tools /net-tools/start-leshan.sh
45 cd tools/net-tools/
46 docker kill net-tools
/Zephyr-latest/boards/telink/tlsr9518adk80d/doc/
Dindex.rst170 `Telink RISC-V Linux Toolchain`_ is available on the `Burning and Debugging Tools for TLSR9 Series …
193 - `Burning and Debugging Tools for all Series`_
194 - `Burning and Debugging Tools for TLSR9 Series`_
195 - `Burning and Debugging Tools for TLSR9 Series in Linux`_
199 - Download `Telink RISC-V Linux Toolchain`_. The toolchain contains tools for the board flashing as…
219 west flash --telink-tools-path=$TELINK_TOOLCHAIN_PATH
257 .. _Telink RISC-V Linux Toolchain: https://wiki.telink-semi.cn/tools_and_sdk/Tools/IDE/telink_riscv…
258 .. _Burning and Debugging Tools for all Series: https://wiki.telink-semi.cn/wiki/IDE-and-Tools/Burn…
259 .. _Burning and Debugging Tools for TLSR9 Series: https://wiki.telink-semi.cn/wiki/IDE-and-Tools/Bu…
260 .. _Burning and Debugging Tools for TLSR9 Series in Linux: https://wiki.telink-semi.cn/wiki/IDE-and…
/Zephyr-latest/samples/net/sockets/tcp/
DREADME.rst16 Compile and start the `net-test-tools`_:
43 .. _`net-test-tools`: https://github.com/intel/net-test-tools

12345678910>>...23