Lines Matching full:models

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
96     the OS, models of peripherals etc. By testing them in conjunction,
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`_.
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
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