Searched full:every (Results 1 – 25 of 684) sorted by relevance
12345678910>>...28
82 0: 1 conv every 16 sec83 1: 1 conv every 8 sec84 2: 1 conv every 4 sec85 3: 1 conv every 2 sec86 4: 1 conv every sec87 5: 2 convs every sec88 6: 4 convs every sec89 7: 8 convs every sec90 8: 16 convs every sec91 9: 32 convs every sec
21 is reported every 30 seconds.29 every 30 seconds.41 every 30 seconds.51 of a thread. The total number of context switches is reported every59 is reported every 30 seconds.66 This number is reported every 30 seconds.74 every 30 seconds.81 is reported every 30 seconds.
54 /// \note MUST REMAIN UNCHANGED: \b osKernelSystemId shall be consistent in every CMSIS-RTOS.57 /// \note MUST REMAIN UNCHANGED: \b osFeature_xxx shall be consistent in every CMSIS-RTOS.81 /// \note MUST REMAIN UNCHANGED: \b osPriority shall be consistent in every CMSIS-RTOS.94 /// \note MUST REMAIN UNCHANGED: \b osWaitForever shall be consistent in every CMSIS-RTOS.98 /// \note MUST REMAIN UNCHANGED: \b osStatus shall be consistent in every CMSIS-RTOS.119 /// \note MUST REMAIN UNCHANGED: \b os_timer_type shall be consistent in every CMSIS-RTOS.126 /// \note MUST REMAIN UNCHANGED: \b os_pthread shall be consistent in every CMSIS-RTOS.130 /// \note MUST REMAIN UNCHANGED: \b os_ptimer shall be consistent in every CMSIS-RTOS.136 /// \note CAN BE CHANGED: \b os_thread_cb is implementation specific in every CMSIS-RTOS.140 /// \note CAN BE CHANGED: \b os_timer_cb is implementation specific in every CMSIS-RTOS.[all …]
28 bool "Measurement every second"31 bool "Measurement every ten seconds"34 bool "Measurement every sixty seconds"37 bool "Measurement every 250 milliseconds"
11 of packet sockets over Ethernet. The sample prints every packet12 received, and sends a dummy packet every 5 seconds.21 packet every 5 seconds. You can use Wireshark to observe these
8 # output being in the range of every few seconds to every few minutes. To
10 Every command is logged with the debug logging level. Use this config26 Once every interval the suppressed commands are logged with the
18 Not every GPIOs are usable for different NCT38XX series. This property28 every GPIOs have pinmux controller functionality. This property
11 can be defined on every board with an Xplained Pro Connector extension and12 every pin can be defined as general purpose GPIO.
12 VOC. The values are fetched and printed every second.20 This sample can run on every board with i2c.
26 host, the device can tell host how many samples on average it needs every frame.28 packets every frame.32 nominal number of samples every frame. Theoretically it should be possible to
158 * regulator and makes host send hardcoded_feedback samples every 16384 SOFs162 * there are nominally 48 samples every SOF. The corresponding value is thus167 * and therefore increment by 1 means 1 additional sample every 2**14 SOFs.169 * 49 samples 1 time during every 16384 SOFs.174 * 48 samples 16383 times and 47 samples 1 time during every 16384 SOFs.179 * during every 512 SOFs.183 * 6 samples every SOF (microframe). The nominal value is the average number of184 * samples to send every microframe and therefore for 48 kHz the nominal value
40 The application will read and print sensor temperature every second. Note that49 <repeats endlessly every second>
11 every 2 seconds and prints them to console.36 you should get a similar output as below, repeated every 2 seconds:
39 data every 2 seconds.52 <repeats endlessly every 2 seconds>
46 /* Prototype of a hook that can be enabled to be called every time the CPU is55 /* Prototype of a hook that can be enabled to be called every time the CPU is
5 # than every 10 ms as each PDU for some reason takes 2 ticks to process.
8 # than every 10 ms as each PDU for some reason takes 2 ticks to process.
