Home
last modified time | relevance | path

Searched refs:in (Results 1 – 10 of 10) sorted by relevance

/nrf_hw_models-latest/tests/zephyr_apps/54_aar_ccm_ecb/src/
Dcommon.h33 static inline void print_byte_array(uint8_t *in, unsigned size) { in print_byte_array() argument
38 printk("0x%02X", in[i]); in print_byte_array()
43 static inline void print_uint32_array(uint32_t *in, unsigned size) { in print_uint32_array() argument
45 printk("0x%08X\n", in[i]); in print_uint32_array()
/nrf_hw_models-latest/docs/
DREADME_HW_models.md21 We are not interested in modeling the particularities of the HW when
34 could, anyhow, not be better than what is described in those.<br>
48 realize, will be modeled as being instantaneous in simulation time.
54 Such processes will be modeled in a bit more complex way:
57 * When needed these timers will be set at a point in the future where some
59 * Whenever that time is reached, the HW scheduler will call a function in that
63 in compile time.
69 Whenever a HW model updates its event timer, it will call a function in the HW scheduler.
75 Note that several HW submodules may be scheduled to run in the same microsecond.
76 In this case, they will be handled in different "delta cycles" in that same microsecond.
[all …]
DGPIO.md5 You can find information about their limitations and approximations in
10 * Do not allow outputs drivers to be in a tristate mode (an output can be disconnected, but not
19 Inputs can be driven in 3 different ways:
32 Any toggle in any pin configured as an output will be dumped to that file, following the
42 if the pin is connected/driven in that direction.
50 unlike in real HW where they are connected to the same physical pins. Note that from the embedded
52 port "0" just like when configuring it in real HW).
65 * Time is a 64 bit unsigned value, representing time in microseconds since boot.
67 * Pin is the pin number in that port (for a nrf52833: 0..31 for port 0, and 0..9 for port 1)
83 Where pin 0 in port 0, is toggled at boot, 200microseconds, 600microseconds, 800microseconds, 1ms
[all …]
DREADME.md4 HAL functions. When used in combination with the real nrfx, these should enable code
14 , so even if you are developing for another variant in that series these models may be enough for
16 Similarly, as the nRF54L15, L10 and L05 only differ in the amount of available RAM and RRAM either
18 It is the intention that models of other Nordic SOCs will be included in the future.
22 If you want to integrate them in another way, please check the section
61 You can find what features of which peripherals are included so far, and with what approximations in
71 in a manner that is comparable to the real HW.
85 Risky in the sense that adding the equivalent register structures would
87 in which they are used in the embedded code; while at the same time these models
91 And unnecessary in the sense that the lack of these peripherals can be hidden
[all …]
DLICENSE42 "Work" shall mean the work of authorship, whether in Source or
44 copyright notice that is included in or attached to the work
45 (an example is provided in the Appendix below).
47 "Derivative Works" shall mean any work, whether in Source or Object
58 submitted to Licensor for inclusion in the Work by the copyright owner
67 designated in writing by the copyright owner as "Not a Contribution."
78 Work and such Derivative Works in Source or Object form.
83 (except as stated in this section) patent license to make, have made,
90 cross-claim or counterclaim in a lawsuit) alleging that the Work
97 Work or Derivative Works thereof in any medium, with or without
[all …]
DUART.md5 You can find information about their limitations and approximations in
8 The UART models are divided in 2 parts:
21 When enabled, the model will dump one line in this file per byte, with two columns:
22 The first column is a timestamp, in microseconds, when the frame *ended*;
59 Remember to use unique paths for each simulation you run in parallel.
70 and that it toggles RTS while there are still 4 spaces left. So even though this will, in some case…
74 the backend will print a warning for each received byte, but the ERRORSRC register in the UART
83 Note that you can also use the loopback backend when connecting a single instance in loopback,
92 in that case, launch it with the `-nosim` option.
/nrf_hw_models-latest/src/nrfx_config/
Dnrfx_config.h15 …ror This file should not be included in builds with Zephyr. Use the one provided by the nordic_hal…
Dnrfx_glue.h19 …ror This file should not be included in builds with Zephyr. Use the one provided by the nordic_hal…
/nrf_hw_models-latest/src/nrfx/hal/
DREADME.md9 There is two main differences in this HAL compared to the real one:
20 of the register itself. For example, in real HW, writting a `1` to
22 When using the HW models, doing this write in itself would only change
27 The original implementation of the HAL APIs from the real nrfx is included in
33 nRFx API corresponding to the peripherals included in these models.
/nrf_hw_models-latest/
DCMakeLists.txt4 # CMake file to compile this BabbleSim component as a west module in Zephyr
11 components folder. More information can be found in\
17 where the simulator is compiled to. More information can be found in\
67 # The nrfx HAL is built in the context of the embedded software
76 # The HW models are built in the runner context, so they have access to the host OS