Home
last modified time | relevance | path

Searched +full:test +full:- +full:on +full:- +full:windows (Results 1 – 25 of 71) sorted by relevance

123

/Zephyr-latest/doc/connectivity/bluetooth/autopts/
Dautopts-linux.rst1 .. _autopts-linux:
3 AutoPTS on Linux
6 This tutorial shows how to setup AutoPTS client on Linux with AutoPTS server running on Windows 10
12 Supported methods to test zephyr bluetooth host:
14 - Testing Zephyr Host Stack on QEMU
16 - Testing Zephyr Host Stack on :ref:`native_sim <native_sim>`
18 - Testing Zephyr combined (controller + host) build on Real hardware (such as nRF52)
29 Install nrftools (only required in the actual hardware test mode)
33 https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Command-Line-Tools/Download.
42 - JLink_Linux_V688a_x86_64.deb
[all …]
Dautopts-win10.rst1 .. _autopts-win10:
3 AutoPTS on Windows 10 with nRF52 board
6 This tutorial shows how to setup AutoPTS client and server to run both on
7 Windows 10. We use WSL1 with Ubuntu only to build a Zephyr project to
8 an elf file, because Zephyr SDK is not available on Windows yet.
15 Update Windows and drivers
18 Update Windows in:
20 Start -> Settings -> Update & Security -> Windows Update
44 Download and install `Git <https://git-scm.com/downloads>`_.
46 consoles. We will use Git Bash as Windows terminal.
[all …]
/Zephyr-latest/tests/bluetooth/classic/sdp_c/
DREADME.rst9 This test suite uses ``bumble`` for testing Bluetooth Classic communication between a host
10 PC (running :ref:`Twister <twister_script>`) and a device under test (DUT) running Zephyr.
15 The test suite has the following prerequisites:
17 * The ``bumble`` library installed on the host PC.
18 The Bluetooth Classic controller on PC side is required. Refer to getting started of `bumble`_
27 ``--hci-transport`` test suite argument (i.e. run ``twister`` with the
28 ``--pytest-args=--hci-transport=usb:0`` argument to use the ``usb:0`` as hci transport for
34 Running on mimxrt1170_evk@B/mimxrt1176/cm7
37 Running the test suite on :ref:`mimxrt1170_evk` relies on configuration of ``bumble``.
39 On the host PC, a HCI transport needs to be required. Refer to `bumble platforms`_ page of
[all …]
/Zephyr-latest/doc/develop/test/
Dtwister.rst3 Test Runner (Twister)
6 Twister scans for the set of test applications in the git repository
7 and attempts to execute them. By default, it tries to build each test
8 application on boards marked as default in the board definition file.
10 The default options will build the majority of the test applications on a
14 Because of the limited test execution coverage, twister
20 When using (at least) one ``-v`` option, twister's console output
21 shows for every test application how the test is run (qemu, native_sim, etc.) or
24 of a test is likewise reported in the ``twister.json`` and other report files.
25 There are a few reasons why twister only builds a test and doesn't run it:
[all …]
/Zephyr-latest/subsys/usb/device/class/dfu/
DKconfig2 # SPDX-License-Identifier: Apache-2.0
8 depends on IMG_MANAGER
22 bool "Generate detach-attach sequence on DFU detach"
28 DFU fails on Windows with WinUSB driver if this is not enabled.
61 WARNING: This bypasses Mcuboot's test-confirm mechanism!
/Zephyr-latest/doc/releases/
Drelease-notes-1.11.rst12 * Thread-level memory protection on x86, ARC and Arm, userspace and memory
14 * Symmetric Multi Processing (SMP) support on the Xtensa architecture.
15 * Initial Armv8-M architecture support.
16 * Native development environment on Microsoft Windows.
17 * Native build target on POSIX platforms.
20 * Firmware over-the-air (FOTA) updates over BLE using MCUmgr.
32 * SMP-aware scheduler
34 * Available on the Xtensa architecture
47 * Armv8-M initial architecture support, including the following cores:
49 * Arm Cortex-M23
[all …]
Drelease-notes-1.6.rst7 release introduces the unified Kernel replacing the separate nano- and
8 micro-kernels and simplifying the overall Zephyr architecture and programming
10 Support for the ARM Cortex-M0/M0+ family was added and board support for
11 Cortex-M was expanded.
22 * Added support for several ARM Cortex-M boards
34 * Added DLIST to operate in all elements of a doubly-linked list.
52 * ARM: Added support for ARM Cortex-M0/M0+.
55 * x86: Changed IRQ controller to return -1 if cannot determine source vector.
64 * Quark SE C1000: Disabled IPM and enabled UART0 on the Sensor Subsystem.
99 * Added raw HCI API to enable physical HCI transport for a Controller-only build.
[all …]
Drelease-notes-1.8.rst13 * Ecosystem: Tracing, debugging support through third-party tools (openocd,
15 * Improved build support on Mac and Windows development environments
39 * arm: Fixed nRF52840-QIAA SoC support for device tree
61 * Support for new ARM board FRDM-KL25Z
66 * arm: Added support for STM32F469I-DISCO board
72 * UART interrupt-driver API is better defined
73 * Support for pull-style console API
89 * HTTP Basic-Auth support added
91 * Add block wise support to CoAP for well-known response
124 * Bluetooth 5.0: The Controller reports itself as 5.0-capable
[all …]
Drelease-notes-1.12.rst12 - Asymmetric multiprocessing (AMP) via integration of OpenAMP
13 - Persistent storage support for Bluetooth Low Energy including Mesh
14 - 802.1Q - Virtual Local Area Network (VLAN) traffic on an Ethernet network
15 - Support multiple concurrent filesystem devices, partitions, and FS types
16 - Ethernet network management interface
17 - Networking traffic prioritization on a per-connection basis
18 - Support for Ethernet statistical counters
19 - Support for TAP net device on the native POSIX port
20 - Command-line Zephyr meta-tool "west"
21 - SPI slave support
[all …]
Drelease-notes-1.13.rst16 * Support for IEEE 802.1AS-2011 generalized Precision Time Protocol (gPTP)
23 * Basic support for Arm TrustZone in Armv8-M
41 * arch: arm: stm32: enable instruction and data caches on STM32F7
42 * arch: arm: implement ARMv8-M MPU driver
44 * arch: arm: macro API for defining non-secure entry functions
48 * arch: ARM: Change the march used by cortex-m0 and cortex-m0plus
50 * arch: arm: basic Arm TrustZone-M functionality for Cortex-M23 and Cortex-M33
51 * arch: arm: built-in stack protection using Armv8-M SPLIM registers
52 * arch: arm: API for using TT intrinsics in Secure/Non-Secure Armv8-M firmware
63 * riscv32: riscv-privilege: Microsemi Mi-V support
[all …]
Drelease-notes-1.5.rst7 1.5.0. This is the first release to follow the 3-month release cadence.
13 - TCP Support
14 - Integration of the Paho MQTT Library support with QoS
15 - Flash Filesystem Support
16 - Integration of the mbedTLS library for encryption
17 - Improved BR/EDR support (for L2CAP, in particular).
18 - Support for the Altera Nios II/f soft CPU architecture
25 - Added nano_fifo_put_list() APIs, which allows queuing a list of elements
26 on a nanokernel FIFO.
27 - Removed unused memory pool structure field.
[all …]
Drelease-notes-2.2.rst18 * Fix CVE-2020-10028
19 * Fix CVE-2020-10060
20 * Fix CVE-2020-10063
21 * Fix CVE-2020-10066
32 * :github:`23494` - Bluetooth: LL/PAC/SLA/BV-01-C fails if Slave-initiated Feature Exchange is disa…
33 * :github:`23485` - BT: host: Service Change indication sent regardless of whether it is needed or …
34 * :github:`23482` - 2M PHY + DLE and timing calculations on an encrypted link are wrong
35 * :github:`23070` - Bluetooth: controller: Fix ticker implementation to avoid catch up
36 * :github:`22967` - Bluetooth: controller: ASSERTION FAIL on invalid packet sequence
37 * :github:`24183` - [v2.2] Bluetooth: controller: split: Regression slave latency during connection…
[all …]
Drelease-notes-1.14.rst17 * CVE-2020-10066
18 * CVE-2020-10069
19 * CVE-2020-13601
20 * CVE-2020-13602
32 * :github:`issuenumber` - issue title
34 * :github:`18334` - DNS resolution is broken for some addresses in master/2.0-pre
35 * :github:`19917` - Bluetooth: Controller: Missing LL_ENC_RSP after HCI LTK Negative Reply
36 * :github:`21107` - LL_ASSERT and 'Imprecise data bus error' in LL Controller
37 * :github:`21257` - tests/net/net_pkt failed on mimxrt1050_evk board.
38 * :github:`21299` - bluetooth: Controller does not release buffer on central side after peripheral …
[all …]
/Zephyr-latest/samples/net/secure_mqtt_sensor_actuator/
DREADME.rst1 .. zephyr:code-sample:: secure-mqtt-sensor-actuator
3 :relevant-api: mqtt_socket sensor_interface
5 Implement an MQTT-based IoT sensor/actuator device
16 - Establishing network connectivity using a DHCPv4 lease
17 - Establishing a secure MQTT connection (using TLS 1.2) to MQTT broker
18 - Publishing temperature sensor data in JSON format to the MQTT broker at a user-defined interval
19 - Subscribing to user-defined topic(s) on MQTT broker
20 - Responding to commands received over the network (LED control)
21 - Handling of MQTT connection, re-connecting and keep-alive
22 - Network status LED
[all …]
/Zephyr-latest/scripts/
Dtwister4 # SPDX-License-Identifier: Apache-2.0
5 """Zephyr Test Runner (twister)
9 This script scans for the set of unit test applications in the git
11 build each test case on one platform per architecture, using a precedence
13 run the tests in any available emulators or simulators on the system.
15 Test cases are detected by the presence of a 'testcase.yaml' or a sample.yaml
17 blocks, each identifying a test scenario. The title of the block is a name for
18 the test case, which only needs to be unique for the test cases specified in
19 that testsuite meta-data. The full canonical name for each test case is <path to
20 test case>/<block>.
[all …]
/Zephyr-latest/doc/develop/
Dbeyond-GSG.rst1 .. _beyond-gsg:
6 The :ref:`getting_started` gives a straight-forward path to set up
7 your Linux, macOS, or Windows environment for Zephyr development. In
11 .. _python-pip:
21 Depending on your operating system, you may need to provide the
22 ``--user`` flag to the ``pip3`` command when installing new packages. This is
25 information about pip\ [#pip]_, including `information on -\\-user`_.
27 - On Linux, make sure ``~/.local/bin`` is at the front of your :envvar:`PATH`
28 :ref:`environment variable <env_vars>`, or programs installed with ``--user``
29 won't be found. Installing with ``--user`` avoids conflicts between pip
[all …]
/Zephyr-latest/doc/develop/flash_debug/
Dhost-tools.rst1 .. _flash-debug-host-tools:
6 This guide describes the software tools you can run on your host workstation to
9 Zephyr's west tool has built-in support for all of these in its ``flash``,
12 file declares that support properly. See :ref:`west-build-flash-debug` for
13 more information on these commands.
17 SAM Boot Assistant (SAM-BA)
20 Atmel SAM Boot Assistant (Atmel SAM-BA) allows In-System Programming (ISP)
22 allows users to develop and program boards with SAM-BA support using
23 :ref:`west <west-flashing>`. Zephyr supports devices with/without ROM
29 .. code-block:: console
[all …]
/Zephyr-latest/scripts/pylib/twister/twisterlib/
Dtestinstance.py3 # Copyright (c) 2018-2025 Intel Corporation
7 # SPDX-License-Identifier: Apache-2.0
42 """Class representing the execution of a particular TestSuite on a platform
44 @param test The TestSuite object we want to build/execute
46 @param base_outdir Base directory for all test results. The actual
47 out directory used is <outdir>/<platform>/<test case name>
80 source_dir_rel = testsuite.source_dir_rel.rsplit(os.pardir+os.path.sep, 1)[-1]
122 def status(self) -> TwisterStatus:
126 def status(self, value : TwisterStatus) -> None:
185 def compose_case_name(self, tc_name) -> str:
[all …]
Denvironment.py4 # Copyright (c) 2018-2025 Intel Corporation
8 # SPDX-License-Identifier: Apache-2.0
45 def _get_installed_packages() -> Generator[str, None, None]:
63 PYTEST_PLUGIN_INSTALLED = 'pytest-twister-harness' in installed_packages
71 def add_parse_arguments(parser = None) -> argparse.ArgumentParser:
79 case_select = parser.add_argument_group("Test case selection",
82 $ ./scripts/twister -v \\
83 --testsuite-root tests/ztest/base \\
84 --testsuite-root tests/kernel \\
85 --test tests/ztest/base/testing.ztest.verbose_0 \\
[all …]
/Zephyr-latest/boards/ezurio/bt510/doc/
Dbt510.rst6 …tooth v5 Long Range integrated sensor that uses a Nordic Semiconductor nRF52840 ARM Cortex-M4F CPU.
14 * :abbr:`I2C (Inter-Integrated Circuit)`
21 * :abbr:`UART (Universal Asynchronous Receiver-Transmitter)`
39 .. zephyr:board-supported-hw::
45 ---
53 ------------
60 -----------------------
67 -------------
77 ------------------
89 :ref:`application_run` for more details on building and running.
[all …]
/Zephyr-latest/doc/contribute/
Dguidelines.rst6 As an open-source project, we welcome and encourage the community to submit
30 on https://github.com and have Git tools available on your development system.
34 (Linux, macOS, and Windows) but some of the tools used in the sections below
35 are only available on Linux and macOS. On Windows, instead of running these
36 tools yourself, you will need to rely on the Continuous Integration (CI)
37 service using Github Actions, which runs automatically on GitHub when you submit
52 https://github.com/zephyrproject-rtos/zephyr/blob/main/LICENSE
54 .. _GitHub repo: https://github.com/zephyrproject-rtos/zephyr
66 https://www.zephyrproject.org/faqs/#1571346989065-9216c551-f523
69 https://www.whitesourcesoftware.com/whitesource-blog/top-10-apache-license-questions-answered/
[all …]
/Zephyr-latest/doc/services/debugging/
Dgdbstub.rst51 * If there are spare UART devices on the board, set ``zephyr,gdbstub-uart``
73 #. Execute GDB on development machine and connect to the GDB stub.
75 .. code-block:: bash
81 .. code-block:: bash
90 There is a test application :zephyr_file:`tests/subsys/debug/gdbstub` with one of its
91 test cases ``debug.gdbstub.breakpoints`` demonstrating how the Zephyr GDB stub can be used.
92 The test also has a case to connect to the QEMU's GDB stub implementation (at a custom
93 port ``tcp:1235``) as a reference to validate the test script itself.
95 Run the test with the following command from your :envvar:`ZEPHYR_BASE` directory:
97 .. code-block:: console
[all …]
/Zephyr-latest/boards/ezurio/bl654_usb/doc/
Dbl654_usb.rst6 The BL654 USB adapter hardware (Ezurio part 451-00004) provides
8 Semiconductor nRF52840 ARM Cortex-M4F CPU.
25 :alt: 451-00004 Box Contents
29 More information about the BL654 USB adapter can be found on the `BL654 USB
30 Dongle Quick Start Guide`_. There is more information on the BL654 range on
39 .. zephyr:board-supported-hw::
48 ---
53 ------------
62 - using the USB connector, which may be used to make the console available on PC as
77 The board supports programming using the built-in bootloader.
[all …]
/Zephyr-latest/scripts/kconfig/
Dmenuconfig.py3 # Copyright (c) 2018-2019, Nordic Semiconductor ASA and Ulf Magnusson
4 # SPDX-License-Identifier: ISC
10 A curses-based Python 2/3 menuconfig implementation. The interface should feel
19 Ctrl-D/U: Page Down/Page Up
27 character in it in the current menu isn't supported. A jump-to feature for
33 F: Toggle show-help mode, which shows the help text of the currently selected
37 C: Toggle show-name mode, which shows the symbol name before each symbol menu
40 A: Toggle show-all mode, which shows all items, including currently invisible
52 When run in standalone mode, the top-level Kconfig file to load can be passed
53 as a command-line argument. With no argument, it defaults to "Kconfig".
[all …]
/Zephyr-latest/doc/connectivity/networking/
Dnative_sim_setup.rst16 In this example, the :zephyr:code-sample:`sockets-echo-server` sample application from
24 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
28 .. code-block:: console
30 git clone https://github.com/zephyrproject-rtos/net-tools
36 For the steps below, you will need three terminal windows:
38 * Terminal #1 is terminal window with net-tools being the current
39 directory (``cd net-tools``)
45 Step 1 - Create Ethernet interface
46 ----------------------------------
[all …]

123