| /Zephyr-latest/doc/connectivity/networking/ |
| D | qemu_user_setup.rst | 3 Networking with QEMU User
11 using QEMU SLIRP with Zephyr.
17 QEMU and uses that stack to implement a virtual NAT'd network. As there are
20 By default, QEMU uses the ``10.0.2.X/24`` network and runs a gateway at
22 this gateway, which will filter out packets based on the QEMU command line
27 More details about User Networking can be obtained from here:
28 https://wiki.qemu.org/Documentation/Networking#User_Networking_.28SLIRP.29
33 In order to use SLIRP with Zephyr, the user has to set the Kconfig option to
34 enable User Networking.
36 .. code-block:: cfg
[all …]
|
| D | networking_with_host.rst | 25 * QEMU using SLIP (Serial Line Internet Protocol).
31 * QEMU using built-in Ethernet driver.
33 * Here IP packets are exchanged between Zephyr and the host system via QEMU's
34 built-in Ethernet driver. Not all QEMU boards support built-in Ethernet so
38 * QEMU using SLIRP (Qemu User Networking).
40 * QEMU User Networking is implemented using "slirp", which provides a full TCP/IP
41 stack within QEMU and uses that stack to implement a virtual NAT'd network. As
42 this support is built into QEMU, it can be used with any model and requires no
47 * Arm FVP (User Mode Networking).
49 * User mode networking emulates a built-in IP router and DHCP server, and
[all …]
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | risc-v.rst | 1 Zephyr support status on RISC-V processors
7 This page describes current state of Zephyr for RISC-V processors.
8 Currently, there's support for some boards, as well as Qemu support
12 Zephyr support includes PMP, :ref:`user mode<usermode_api>`, several
15 User mode and PMP support
19 it on Zephyr allows user space support and stack protection to be
35 SMP is supported on RISC-V for both QEMU-virtualized and hardware-based
37 :zephyr:board:`qemu_riscv32` or :zephyr:board:`qemu_riscv64` for QEMU-based
39 hardware-based platforms.
|
| /Zephyr-latest/doc/develop/ |
| D | beyond-GSG.rst | 1 .. _beyond-gsg:
6 The :ref:`getting_started` gives a straight-forward path to set up
11 .. _python-pip:
22 ``--user`` flag to the ``pip3`` command when installing new packages. This is
24 See `Installing Packages`_ in the Python Packaging User Guide for more
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
30 and the system package manager, and is the default on Debian-based
[all …]
|
| /Zephyr-latest/samples/drivers/ipm/ipm_ivshmem/ |
| D | README.rst | 1 .. zephyr:code-sample:: ipm-ivshmem
3 :relevant-api: ipm_interface
5 Implement inter-processor mailbox (IPM) over IVSHMEM (Inter-VM shared memory)
10 * QEMU needs to available.
12 ivshmem-server needs to be available and running. The server is available in
13 Zephyr SDK or pre-built in some distributions. Otherwise, it is available in
14 QEMU source tree.
16 ivshmem-client needs to be available as it is employed in this sample as an
17 external application. The same conditions of ivshmem-server apply to the
18 ivshmem-server, as it is also available via QEMU.
[all …]
|
| /Zephyr-latest/snippets/xen_dom0/ |
| D | README.rst | 9 This snippet allows user to build Zephyr as a Xen initial domain (Dom0). The feature
16 * add correct memory and hypervisor nodes, based on regions Xen picked for Domain-0 on your setup.
25 .. code-block:: console
27 west build -b qemu_cortex_a53 -S xen_dom0 samples/synchronization
29 QEMU example with Xen
33 directory of this snippet is QEMU Xen control domain example.
37 * fetch and build Xen (e.g. RELEASE-4.17.0) for arm64 platform
41 For starting you can use QEMU from Zephyr SDK by following command:
43 .. code-block:: console
45 <path to Zephyr SDK>/sysroots/x86_64-pokysdk-linux/usr/bin/qemu-system-aarch64 -cpu cortex-a53 \
[all …]
|
| /Zephyr-latest/samples/drivers/virtualization/ivshmem/doorbell/ |
| D | README.rst | 1 .. zephyr:code-sample:: ivshmem-doorbell
3 :relevant-api: ivshmem
5 Use Inter-VM Shared Memory to exchange messages between two processes running on different
18 QEMU needs to available.
20 ivshmem-server needs to be available and running. The server is available in
21 Zephyr SDK or pre-built in some distributions. Otherwise, it is available in
22 QEMU source tree.
24 ivshmem-client needs to be available as it is employed in this sample as an
25 external application. The same conditions of ivshmem-server applies to the
26 ivshmem-server, as it is also available via QEMU.
[all …]
|
| /Zephyr-latest/boards/arm/mps2/ |
| D | board.cmake | 1 # SPDX-License-Identifier: Apache-2.0
2 # Copyright 2024 Arm Limited and/or its affiliates <open-source-office@arm.com>
5 set(SUPPORTED_EMU_PLATFORMS qemu armfvp)
6 set(QEMU_CPU_TYPE_${ARCH} cortex-m3)
8 -cpu ${QEMU_CPU_TYPE_${ARCH}}
9 -machine mps2-an385
10 -nographic
11 -vga none
13 set(ARMFVP_BIN_NAME FVP_MPS2_Cortex-M3)
16 set(ARMFVP_BIN_NAME FVP_MPS2_Cortex-M0plus)
[all …]
|
| /Zephyr-latest/doc/services/tfm/ |
| D | requirements.rst | 1 TF-M Requirements
4 The following are some of the boards that can be used with TF-M:
6 .. list-table::
7 :header-rows: 1
9 * - Board
10 - NSPE board name
11 * - :ref:`mps2_an521_board`
12 - ``mps2/an521/cpu0/ns`` (qemu supported)
13 * - :ref:`mps3_board`
14 - ``mps3/corstone300/an547/ns`` (qemu supported)
[all …]
|
| /Zephyr-latest/boards/qemu/nios2/doc/ |
| D | index.rst | 6 This board configuration will use QEMU to emulate the Altera MAX 10 platform.
8 This configuration provides support for an Altera Nios-II CPU and these devices:
25 +--------------+------------+----------------------+
28 | IIC | on-chip | Internal interrupt |
30 +--------------+------------+----------------------+
31 | NS16550 | on-chip | serial port |
33 +--------------+------------+----------------------+
34 | TIMER | on-chip | system clock |
35 +--------------+------------+----------------------+
42 ------------
[all …]
|
| /Zephyr-latest/samples/drivers/ethernet/eth_ivshmem/ |
| D | README.rst | 1 .. zephyr:code-sample:: eth-ivshmem
2 :name: Inter-VM Shared Memory (ivshmem) Ethernet
3 :relevant-api: ivshmem ethernet
14 Building Jailhouse Linux for QEMU
20 .. code-block:: console
22 git clone https://github.com/siemens/jailhouse-images.git
23 cd jailhouse-images
26 Open the menu, select "QEMU ARM64 virtual target" then "Save & Build"
29 .. code-block:: console
31 ./kas-container menu
[all …]
|
| /Zephyr-latest/samples/net/stats/ |
| D | README.rst | 1 .. zephyr:code-sample:: net-stats
3 :relevant-api: net_stats
5 Query and display network statistics from a user application.
10 This sample shows how to query (and display) network statistics from a user
19 - :ref:`networking_with_host`
24 A good way to run this sample application is with QEMU or native_sim board
29 .. zephyr-app-commands::
30 :zephyr-app: samples/net/stats
39 .. code-block:: console
55 TCP seg rsterr 0 rst 0 re-xmit 0
|
| /Zephyr-latest/samples/net/promiscuous_mode/ |
| D | README.rst | 1 .. zephyr:code-sample:: net-promiscuous-mode
3 :relevant-api: promiscuous
14 The application will also provide a shell so that user can enable
21 - :ref:`networking_with_host`
26 There are multiple ways to use this application. In this example QEMU
29 .. zephyr-app-commands::
30 :zephyr-app: samples/net/promiscuous_mode
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig | 6 # SPDX-License-Identifier: Apache-2.0
61 module-dep = NET_LOG
62 module-str = Log level for PMTU
63 module-help = Enables PMTU to output debug messages.
80 Enables TCP/IP stack to be offload to a co-processor.
92 module-dep = NET_LOG
93 module-str = Log level for offload layer
94 module-help = Enables offload layer to output debug messages.
108 prompt "Qemu networking"
114 from inside qemu to host system. This can be done either via
[all …]
|
| /Zephyr-latest/scripts/logging/dictionary/ |
| D | log_parser.py | 6 # SPDX-License-Identifier: Apache-2.0
9 Log Parser for Dictionary-based Logging
35 argparser.add_argument("--hex", action="store_true",
37 argparser.add_argument("--rawhex", action="store_true",
39 argparser.add_argument("--debug", action="store_true",
60 with open(args.logfile, "r", encoding="iso-8859-1") as hexfile:
78 # When running QEMU via west or ninja, there may be additional
79 # strings printed by QEMU, west or ninja (for example, QEMU
80 # is terminated, or user interrupted, etc). So we need to
88 idx -= 2
|
| /Zephyr-latest/samples/bluetooth/mesh_provisioner/ |
| D | README.rst | 1 .. zephyr:code-sample:: ble_mesh_provisioner
3 :relevant-api: bt_mesh bluetooth
20 ``sw0`` :ref:`devicetree <dt-guide>` alias, the application then waits
21 for the user to press the button, which will trigger provisioning using
22 PB-ADV. If the board doesn't have the push button, the sample will
35 * QEMU with BlueZ running on the host
43 See :zephyr:code-sample-category:`bluetooth` samples for details on
44 how to run the sample inside QEMU.
48 .. zephyr-app-commands::
49 :zephyr-app: samples/bluetooth/mesh_provisioner
[all …]
|
| /Zephyr-latest/boards/qemu/cortex_m3/doc/ |
| D | index.rst | 6 This board configuration will use QEMU to emulate the TI LM3S6965 platform.
8 This configuration provides support for an ARM Cortex-M3 CPU and these devices:
25 +--------------+------------+----------------------+
28 | NVIC | on-chip | nested vectored |
30 +--------------+------------+----------------------+
31 | Stellaris | on-chip | serial port |
33 +--------------+------------+----------------------+
34 | SYSTICK | on-chip | system clock |
35 +--------------+------------+----------------------+
42 ------------
[all …]
|
| /Zephyr-latest/boards/qemu/cortex_m0/doc/ |
| D | index.rst | 6 This board configuration will use QEMU to emulate the
9 This configuration provides support for an ARM Cortex-M0 CPU and these devices:
25 +--------------+------------+----------------------+
28 | NVIC | on-chip | nested vectored |
30 +--------------+------------+----------------------+
31 | nRF | on-chip | serial port |
33 +--------------+------------+----------------------+
34 | nRF TIMER | on-chip | system clock |
35 +--------------+------------+----------------------+
42 ------------
[all …]
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-tools.rst | 1 .. _bluetooth-tools:
14 .. _bluetooth-mobile-apps:
54 .. code-block:: console
58 ./bootstrap-configure --disable-android --disable-midi
67 and making sure to include the :literal:`-E` option in the daemon's execution
70 .. code-block:: console
72 ExecStart=/usr/libexec/bluetooth/bluetoothd -E
76 .. code-block:: console
78 sudo systemctl daemon-reload
83 Running on QEMU or native_sim
[all …]
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | handlers.py | 4 # Copyright (c) 2018-2022 Intel Corporation
8 # SPDX-License-Identifier: Apache-2.0
39 print("Install pyserial python module with pip to use --device-testing option.")
45 pass # "--device-serial-pty" option is not supported on Windows OS
124 _d_suite = detected_suite_names[-len(expected_suite_names):]
170 # Note: for targets using QEMU, we assume that the target will
220 this_timeout = timeout_time - time.time()
227 line_decoded = self.line.decode('utf-8', "replace")
230 stripped_line = stripped_line[:-len(suffix)].rstrip()
272 command = ["renode-test",
[all …]
|
| /Zephyr-latest/arch/common/ |
| D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0
7 bool "Semihosting support for ARM and RISC-V targets"
11 RISC-V target to communicate and use the Input/Output facilities on
14 https://developer.arm.com/documentation/dui0471/m/what-is-semihosting-
15 https://github.com/riscv/riscv-semihosting-spec/blob/main/riscv-semihosting-spec.adoc
16 This option is compatible with hardware and with QEMU, through the
17 (automatic) use of the -semihosting-config switch when invoking it.
44 The ARMv6-M, ARMv7-M, and ARMv8-R MPU MPU architecture requires a power-of-two
47 The NXP MPU as well as the ARMv8-M MPU do not require MPU regions
48 to have power-of-two alignment for base address and region size.
[all …]
|
| /Zephyr-latest/boards/arm/mps3/doc/ |
| D | index.rst | 12 - Nested Vectored Interrupt Controller (NVIC)
13 - System Tick System Clock (SYSTICK)
14 - Cortex-M System Design Kit GPIO
15 - Cortex-M System Design Kit UART
16 - Ethos-U55 NPU
17 - AN547 and AN552 support Arm Cortex-M55 CPU
18 - AN555 support Arm Cortex-M85 CPU
24 `Corstone-300 FVP`_/`Corstone-310 FVP`_ (Fixed Virtual Platforms) is a complete
28 Ethos-U55 NPU, which is unavailable in QEMU or other simulation platforms.
36 .. tab:: MPS3 Corstone-300 (AN547)
[all …]
|
| /Zephyr-latest/doc/develop/debug/ |
| D | index.rst | 11 This section is a quick hands-on reference to start debugging your
12 application with QEMU. Most content in this section is already covered in
13 `QEMU`_ and `GNU_Debugger`_ reference manuals.
15 .. _QEMU: http://wiki.qemu.org/Main_Page
23 The simplest way to debug an application running in QEMU is using the GNU
24 Debugger and setting a local GDB server in your development system through QEMU.
37 QEMU instance with the processor halted at startup and with a GDB server
40 Running QEMU directly
43 You can run QEMU to listen for a "gdb connection" before it starts executing any
46 .. code-block:: bash
[all …]
|
| /Zephyr-latest/tests/benchmarks/sched_userspace/src/ |
| D | main.c | 4 * SPDX-License-Identifier: Apache-2.0
15 #include "user.h"
33 * precision. In practice it's VERY jittery in recent qemu in stamp()
54 thread->partition, in yielder_entry()
57 ret = k_mem_domain_init(&thread->domain, ARRAY_SIZE(parts), parts); in yielder_entry()
64 k_mem_domain_add_thread(&thread->domain, k_current_get()); in yielder_entry()
95 * this way, user threads all start together in exec_test()
96 * (lower number --> higher prio) in exec_test()
109 uint32_t full_time = stamps[MEAS_END] - stamps[MEAS_START]; in exec_test()
112 printk("Swapping %2u threads: %8" PRIu32 " cyc & %6" PRIu32 " rounds -> %6" in exec_test()
[all …]
|
| /Zephyr-latest/samples/kernel/bootargs/ |
| D | README.rst | 1 .. zephyr:code-sample:: bootargs
26 .. zephyr-app-commands::
27 :zephyr-app: samples/kernel/bootargs
35 .. code-block:: console
37 *** Booting Zephyr OS build v3.7.0-514-gd4490bc739d1 ***
47 .. zephyr-app-commands::
48 :zephyr-app: samples/kernel/bootargs
56 .. code-block:: console
58 *** Booting Zephyr OS build v3.7.0-rc2-421-g3cf718e6dabc ***
59 argv[0] = /home/user/zephyr/samples/kernel/bootargs/build/zephyr/zephyr.elf
[all …]
|
