Searched refs:called (Results 151 – 175 of 279) sorted by relevance
12345678910>>...12
93 The counter API callback is called at the correct time::
217 mqx_upload_on_m4SoloX which can be called directly to load Zephyr applications.240 so it will succeed when called again. Then it can have this output below:
169 * The config option :kconfig:option:`CONFIG_LV_Z_FLUSH_THREAD_PRIO` is now called173 * The config option :kconfig:option:`CONFIG_LV_Z_VBD_CUSTOM_SECTION` is now called600 :c:func:`bt_pacs_register` also have to be called before :c:func:`bt_ascs_register` can be601 be called. All Kconfig options still remain. Runtime configuration cannot override a disabled
64 the one called :zephyr:code-sample:`hello_world`.
264 * set correctly, the brk_s instruction will be called
56 This product has the onboard debugger circuit, J-Link On-Board (hereinafter called “J-Link-OB”). Yo…
173 :code:`bt adv-data` or :code:`bt advertise` must be called again to set the new advertising data.
136 If a MQTT message is received, an MQTT callback function will be called and an
195 This new management procedure could then be called by using:
85 :c:func:`sys_multi_mem_blocks_alloc` is called with an opaque
179 so-called backdoor is enabled (via option
162 If enabled and cbvprint_package() is called with the corresponding
180 (``list_symbols``), and the hello_world function which the extension exports can be called and
36 may be called to release any runtime-allocated buffers the object was using.213 must have :c:func:`k_object_init` called on it at some point by a supervisor
272 thread as the Zephyr code would be called from the wrong context,313 ``bs_tests`` also provides a hook which will be called from the embedded application322 ticks. When these ticks occur a registered test tick function will be called.
343 This final executable is typically called ``zephyr.exe`` and can be run or debugged just like any477 The soc_inf layer provides a special type of hook called the NATIVE_TASKS.479 These allow registering (at build/link time) embedded context functions which will be called
57 is called until all RPL entries are written to the flash.
229 `nrf_802154_assert_handler()` is called. File and line debug information are not provided
85 in the monitored socket, a user supplied work is called.271 (called socket dispatcher), allowing to select an offloaded network
112 illegal if called on a runnable thread. The thread must be blocked or324 :c:func:`arch_switch` is always called with interrupts masked, and takes344 registers only when :c:func:`arch_switch` is called to minimize context
24 will be called and run once per test suite run.361 called directly.429 function (different for each context) is called and then the context sleeps for
120 When the write function is called, the magic header and checksum (if enabled)
168 Note that this may be called multiple times for each file read and
186 so-called backdoor is enabled (via option
163 This target uses a third-party tool called puncover which can be found at
