Lines Matching +full:line +full:- +full:idle +full:- +full:low
3 Native simulator - native_sim
63 .. zephyr-app-commands::
64 :zephyr-app: samples/hello_world
65 :host-os: unix
77 .. code-block:: console
82 This executable accepts several command line options depending on the
84 You can run it with the ``--help`` command line switch to get a list of
87 .. code-block:: console
89 $ ./build/zephyr/zephyr.exe --help
92 finished. It simply goes into the idle loop forever.
95 Application tests using the :ref:`ztest framework<test-framework>` will exit after all
118 (e.g., ``-O0``) by setting :kconfig:option:`CONFIG_NO_OPTIMIZATIONS`.
129 ``west build`` or ``cmake`` command line invocation.
142 ``west build`` or ``cmake`` command line invocation.
170 LP64 ABI (x86-64 in x86 systems), where pointers and longs are 64 bits.
243 You can do this with the ``--rt`` and ``--no-rt`` options from the command line.
259 This can be controlled with the ``--rt-ratio=<ratio>`` and ``-rt-drift=<drift>``
260 command line options. Note that both of these options control the same
262 ``ratio - 1``.
266 In this way if, for example, ``--rt-ratio=2`` is given, the simulated time
268 Similarly if ``--rt-drift=-100e-6`` is given, the simulated time will progress
270 Note that these 2 options have no meaning when running in non real-time
274 -----------------------------------------------------
279 st = (rt - last\_rt) \times ratio + last\_st
281 And vice-versa:
284 rt = (st - last\_st) / ratio + last\_rt
316 pseudo-tty. For more information refer to the section `PTTY UART`_.
319 An UART driver for interacting with host-attached serial port devices
327 This RTC can also be set to start from time 0 with the ``--rtc-reset`` command
328 line option.
331 ``--rtc-offset=<offset>`` option,
341 - ``RTC_CLOCK_BOOT``: It counts the simulated time passed since boot.
343 - ``RTC_CLOCK_REALTIME``: RTC persistent time. It is affected by
345 - ``RTC_CLOCK_PSEUDOHOSTREALTIME``: A version of the real host time,
362 You can change this random seed value by using the command line option:
363 :samp:`--seed={<random_seed>}` where the value specified is a 32-bit integer
371 network interface can be created by the ``net-setup.sh`` script found in
372 the `net-tools`_ zephyr project repository. User can communicate with the
379 .. _`net-tools`: https://github.com/zephyrproject-rtos/net-tools
399 a command line option to ``zephyr.exe``. For example, to use ``hci0``,
400 use ``sudo zephyr.exe --bt-dev=hci0``. Using the device requires root
403 must be powered down and support Bluetooth Low Energy (i.e. support the
410 address 127.0.0.0 and port number 1020 use ``zephyr.exe --bt-dev=127.0.0.1:1020``.
428 When building for the default 32bit ``native_sim`` target this driver requires a 32-bit version of
431 You may also need to set ``pkg-config`` to correctly pickup the SDL2 install path.
433 On Ubuntu the package is ``libsdl2-dev`` whose 64bit version is likely installed by default.
434 On an Ubuntu 18.04 host system, you can install the ``pkg-config`` and the 32bit
435 ``libsdl2-dev:i386`` packages, and configure the pkg-config search path with these commands:
437 .. code-block:: console
439 $ sudo dpkg --add-architecture i386
441 $ sudo apt-get install pkg-config libsdl2-dev:i386
442 $ export PKG_CONFIG_PATH=/usr/lib/i386-linux-gnu/pkgconfig
453 can select the location of this file and its name with the command line parameter ``--eeprom``.
464 command line parameter ``--flash``. The flash data will be stored in raw format
484 .. code-block:: dts
487 compatible = "zephyr,native-linux-evdev";
490 The application then has to be run with a command line option to specify
492 ``zephyr.exe --evdev=/dev/input/event0``.
497 :dtcompatible:`zephyr,input-sdl-touch`.
505 :dtcompatible:`zephyr,native-linux-can`.
507 It is possible to specify which CAN interface will be used by the app using the ``--can-if``
508 …command-line option. This option overrides **every** Linux SocketCAN driver instance to use the sp…
534 newly created UART pseudo-terminal will be displayed in the console.
538 .. code-block:: console
540 $ xterm -e screen /dev/<ttyn> &
545 by passing the command line option ``-attach_uart`` to the executable.
546 The command used for attaching to the new shell can be set with the command line
547 option ``-attach_uart_cmd=<"cmd">``. Where the default command is given by
553 Neither runtime configuration or line control are supported.
565 with ``"zephyr,native-tty-uart"`` compatible property and ``okay`` status, such
568 .. code-block:: dts
572 compatible = "zephyr,native-tty-uart";
573 serial-port = "/dev/ttyUSB0";
574 current-speed = <115200>;
580 properties ``serial-port`` and ``current-speed`` respectively. The
581 ``serial-port`` property is optional.
582 * Serial port and baud rate can also be set via command line options ``X_port``
583 and ``X_baud`` respectively, where ``X`` is a name of a node. Command line
587 * This driver can emulate an interrupt-driven UART by enabling
592 The :zephyr:code-sample:`uart-native-tty` sample app provides a working example of the
597 It has runtime configuration support, but no line control support.
626 with the command line options ``--color``, ``--no-color`` and
627 ``--force-color``.
661 current working directory. This directory can be changed via the command line
662 option ``--flash-mount``. As this directory operates as a mount point for FUSE
670 .. code-block:: console
672 $ fusermount -u flash
674 Note that this feature requires a 32-bit version of the FUSE library, with a
675 minimal version of 2.6, on the host system and ``pkg-config`` settings to
678 On a Ubuntu 22.04 host system, for example, install the ``pkg-config`` and
679 ``libfuse-dev:i386`` packages, and configure the pkg-config search path with
682 .. code-block:: console
684 $ sudo dpkg --add-architecture i386
686 $ sudo apt-get install pkg-config libfuse-dev:i386
687 $ export PKG_CONFIG_PATH=/usr/lib/i386-linux-gnu/pkgconfig
697 .. csv-table:: Drivers/backends vs libC choice