Home
last modified time | relevance | path

Searched full:run (Results 1 – 10 of 10) sorted by relevance

/nrf_hw_models-3.6.0/.github/workflows/
Dbuild.yml20 run: |
29 run: |
39 run: |
/nrf_hw_models-3.6.0/docs/
DREADME_HW_models.md11 and run long simulations fast.<br>
64 Note that several HW submodules may be scheduled to run in the same microsecond.
171 When two events times coincide, the one with the highest priority should be run first,
172 and when two have the same priority, it does not matter which is run first, while
173 they are run in the same order consistently.
DREADME.md5 meant for the nrfx to run without needing further changes.
64 These models are accurate enough to allow the current Zephyr to run, and
67 In general, functionality is modelled only to the necessary degree as to enable the SW to run,
DUART.md58 Remember to use unique paths for each simulation you run in parallel.
/nrf_hw_models-3.6.0/src/nrfx/hal/
DREADME.md6 Its main purpose is to allow unmodified embedded code to run directly
/nrf_hw_models-3.6.0/make_inc/
Dcommon_post.mk41 $(error Required library ($@) not found. Run top level make to build all dependencies in order)
/nrf_hw_models-3.6.0/src/HW_models/
DNRF_HWLowL.c15 * to run the phy. It can be useful if for example the device crashes
DNHW_CLOCK.c27 * able to run the radio. The radio models will run just fine without it.
DNHW_RADIO.c107 …s set to the time anything may decide to stop. Which for simplicity is whenever *anything* may run.
DNRF5340_peri_types.h741 /* Bits 17..16 : Radio data rate that the CCM shall run synchronous with */