Lines Matching full:embedded

22 and execute the embedded code natively on Linux.
51 integration testing of embedded code on workstation/simulation.
56 embedded HW.
58 These tests are run in workstation, that is, without using real embedded HW.
77 methodologies normally employed by embedded SW developers and how they relate
95   - Using bsim boards: Allow testing the embedded SW (or a subset), including
103     test the embedded code under test while controlling the test from external
104     python test scripts. This is supported by compiling the embedded code with
106     and an embedded application that handles the RPC calls themselves, while
109     the embedded code, but without any specific HW. In that way, many embedded
117   Based on dedicated embedded test applications build with the code under test.
118   The embedded test application is responsible for driving the tests and check
131 As shown in the figure below, when you build your embedded application targeting one of Zephyr's
137 And then both the embedded SW and runner are linked together to produce a Linux executable.
191     Overall architecture in a Zephyr application in an embedded target vs a bsim
304 These tests are built together with the embedded SW, and are present in the
313 ``bs_tests`` also provides a hook which will be called from the embedded application
335 Note also that, for AMP targets like the :ref:`nrf5340bsim <nrf5340bsim>`, each embedded MCU has
352 - Test (bs_tests) control: To select a test for each embedded CPU,
364   target architecture. If this is not the case, embedded code which works in one
367 - WordSize: The bsim targets, as well as normal embedded targets are 32 bit