Lines Matching +full:execution +full:- +full:memory
22 Zephyr application, eliminating the need for architecture-specific
56 You must have the 32-bit C library installed in your system
57 (in Ubuntu 16.04 install the gcc-multilib package)
67 for Linux (WSL1) because WSL1 does not support native 32-bit binaries.
72 <https://github.com/microsoft/WSL/issues/2468#issuecomment-374904520>`_ it
102 - There can **not** be busy wait loops in the application code that wait for
105 will stall the execution. For example, the following busy wait loop code,
106 which could be interrupted on actual hardware, will stall the execution of
109 .. code-block:: c
117 .. code-block:: c
123 - Code that depends on its own execution speed will normally not
127 .. code-block:: c
129 peripheral_x->run = true;
137 - This port is not meant to, and could not possibly help debug races between
140 - You may not use hard coded memory addresses because there is no I/O or
149 pause it after the execution is stuck; it will be paused in
163 .. code-block:: c
198 - Allow functional debugging, instrumentation and analysis of the code with
200 - Allow functional regression testing, and simulations in which we have the
202 - Run tests fast: several minutes of simulated time per wall time second.
203 - Possibility to connect to external tools which may be able to run much
205 - Deterministic, repeatable runs:
210 - Debugging or instrumenting the code.
211 - Pausing in a breakpoint and continuing later.
212 - The host computer performance or its load.
233 :figclass: align-center
236 dimensions: Having the real memory map or emulating the exact time an
246 The problem of how to emulate the instruction execution speed is solved
249 There is no I/O or MMU emulation. If you try to access memory through hardcoded
259 Execution is fully reproducible, you can pause it without side-effects.
265 your desired board. For example an ARM based one. QEMU emulates the real memory
271 QEMU cannot provide any emulation of execution speed. It simply
274 as the execution speed depends on the host system performance and its load.
281 Execution is not reproducible. Some bugs may be triggered only in some runs
288 your real CPU/platform or a close enough relative. The memory layout is modeled
299 Execution is fully reproducible. You can normally pause your execution without
300 side-effects.
322 :figclass: align-center
330 :figclass: align-center
338 The result of this build is a pre-linked elf library, which contains what we can call the
364 It is worth noting that the embedded SW library is first pre-linked. That is that all symbols which
393 …tps://github.com/BabbleSim/native_simulator/blob/main/docs/Design.md#build-and-symbol-visibility>`_
417 variables. The Zephyr stacks (which are allocated in "static memory") are
421 and typically as a 32-bit binary assuming pointer and integer types are 32-bits
444 The overall execution and scheduling is handled by the native simulator runner itself, which calls
447 …tation <https://github.com/BabbleSim/native_simulator/blob/main/docs/Design.md#overall-execution>`_
468 …documentation <https://github.com/BabbleSim/native_simulator/blob/main/docs/Design.md#busy-waits>`_
480 at different stages during the process execution: Before command line parsing
487 …s <https://github.com/BabbleSim/native_simulator/blob/main/docs/Design.md#native-simulator-tasks>`_