Lines Matching refs:will
30 | Some components, code, options names, and documentation will still use the old native_posix
31 names. But all components which worked with native_posix will work with native_sim.
95 Application tests using the :ref:`ztest framework<test-framework>` will exit after all
131 Note that you will need the ASan library installed in your system.
160 The 32 bit version, ``native_sim``, is the default target, which will compile
179 By default it will be compiled with the host C library (:kconfig:option:`CONFIG_EXTERNAL_LIBC`),
183 :ref:`Picolibc <c_library_picolibc>` will be selected by default instead.
186 you will build your code in a more similar way as when building for the embedded target,
187 you will be able to test your code interacting with that C library,
188 and there will be no conflicts with the :ref:`POSIX OS abstraction<posix_support>` shim,
189 but, accessing the host for test purposes from your embedded code will be more
190 difficult, and you will have a limited choice of
235 HW models. Therefore any normal Zephyr thread will also know only about
252 So if the host load is too high, or you are running in a debugger, you will
267 will advance at twice the real time speed.
268 Similarly if ``--rt-drift=-100e-6`` is given, the simulated time will progress
348 this value will be a couple of hundredths of microseconds ahead of the
360 This device will generate the same sequence of random numbers if initialized
464 command line parameter ``--flash``. The flash data will be stored in raw format
465 and the file will be truncated to match the size specified in the devicetree
466 configuration. In case the file does not exists the driver will take care of
507 It is possible to specify which CAN interface will be used by the app using the ``--can-if``
534 newly created UART pseudo-terminal will be displayed in the console.
616 Otherwise :kconfig:option:`CONFIG_UART_CONSOLE` will be set to select the UART as
665 On exit, the native_sim board application will take care of unmounting the