Lines Matching full:hw
34 .. _Architecture of HW models used for FW development and testing:
43 .. _nRF HW models design documentation:
55 will include some HW models which, to some degree, pretend to be the real
56 embedded HW.
58 These tests are run in workstation, that is, without using real embedded HW.
60 without the need for real HW, and in a deterministic/reproducible fashion.
85 - Integration tests on real HW: Allows testing with the real SW
86 components that may be too dependent on the exact HW particularities, and
89 but at the expense of slower execution, needing the real HW setups,
109 the embedded code, but without any specific HW. In that way, many embedded
110 components which are dependent on the HW would not be suited for testing in
128 Relationship between Zephyr, the native simulator, the nRF HW models and BabbleSim
133 expanded by the nRF HW models for that target.
136 The native simulator runner is built together with the HW models which match your desired target.
144 Relationship between Zephyr, the native simulator, the nRF HW models and BabbleSim.
169 HW models thread ( See `Threading`_ ).
171 selecting the HW models which are built in the native simulator runner context, IRQ handling,
206 Threading and overall scheduling of CPU and HW models
215 `Architecture of HW models used for FW development and testing`_
216 a general introduction to the babblesim HW models and their scheduling are provided.
219 `nRF HW models design documentation`_.
228 as needed to the next scheduled HW event, and does not progress while
236 The native simulator HW scheduler provides the overall HW event time loop
237 required by the HW models, which consists of a very simple
246 The same considerations as for the HW models apply to the bsim boards, see
247 `Architecture of HW models used for FW development and testing`_.
271 In particular, one should not call Zephyr APIs from the original/HW models
310 There is a set of one time hooks at different levels of initialization of the HW
319 dedicated test "task". This will be executed in the HW models thread context,
349 - The HW models command line arguments: The HW models will expose which