Home
last modified time | relevance | path

Searched refs:should (Results 501 – 525 of 1262) sorted by relevance

1...<<21222324252627282930>>...51

/Zephyr-latest/boards/st/stm32h747i_disco/doc/
Dindex.rst104 - **SB21**, **SB45** and **R87** should be opened
105 - **SB22**, **SB44**, **SB17** and **SB8** should be closed
160 Applications for the ``stm32h747i_disco`` board should be built per core target,
232 You should see the following message on the console:
/Zephyr-latest/boards/96boards/carbon/doc/
Dstm32f401xe.rst24 - The ``96b_carbon/nrf51822`` configuration should be used for programming
270 The board should power ON. Force the board into DFU mode by keeping the BOOT0
289 You should see following confirmation on your Linux host:
320 Press the Reset button and you should see the following message in your
/Zephyr-latest/doc/connectivity/bluetooth/autopts/
Dautopts-linux.rst115 If you type 'ifconfig' in terminal, you should be able to find your host IP:
209 With VirtualBox there should be no problem. Just find dongle in Devices -> USB and connect.
251 On Linux, go to ~/zephyrproject. There should be already ~/zephyrproject/build
389 One or more of the following steps should help:
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_l2.rst49 if the network stack should then handle it.
83 In the next section, we will describe how a device driver should behave when
92 :c:struct:`net_pkt` and should be allocated through
134 radio drivers should not have to care about. This is why the
/Zephyr-latest/doc/kernel/services/other/
Dfatal.rst159 :c:func:`k_oops()`. This should be used to indicate an unrecoverable condition
168 :c:func:`k_panic()`. This should be used to indicate that the Zephyr kernel is
170 :c:func:`k_sys_fatal_error_handler()` should not return if the kernel
209 should be treated as a very serious condition impacting the health of the
/Zephyr-latest/boards/st/stm32wb5mmg/doc/
Dstm32wb5mmg.rst165 To operate bluetooth on STM32WB5MMG, Cortex-M0 core should be flashed with
174 anymore for a use in Zephyr and only "HCI Only" versions should be used on the M0
217 STM32WB5MMG module. To do this you should put SW4 on OFF and SW5 on ON mode.
262 Rest the board and you should see the following messages on the console:
/Zephyr-latest/tests/benchmarks/thread_metric/
Dthread_metric_readme.txt15 should execute the same on every operating system. Test values
16 from testing with different RTOS products should be scaled
25 to make sure they are valid (should all be within 1 of the same
245 1. Time period should be 30 seconds. This will ensure the printf
/Zephyr-latest/soc/nxp/imxrt/
DKconfig.defconfig93 # have L1 instruction and data caches that should be enabled at boot
/Zephyr-latest/boards/arm/mps3/
Dboard.cmake38 # default is '0x11000000' but should match cpu<i>.INITSVTOR which is 0.
/Zephyr-latest/subsys/mgmt/mcumgr/grp/settings_mgmt/
DKconfig31 therefore the MCUmgr stack should be appropriately sized.
/Zephyr-latest/subsys/mgmt/mcumgr/transport/
DKconfig.udp9 # Options defined in this file should be prefixed:
/Zephyr-latest/doc/services/task_wdt/
Dindex.rst32 The maximum number of channels is predefined via Kconfig and should be adjusted
/Zephyr-latest/doc/connectivity/networking/
Dqemu_802154_setup.rst76 You should see data passed between the two QEMUs.
/Zephyr-latest/samples/net/sockets/dumb_http_server_mt/
DREADME.rst43 You should see a page with a sample content about Zephyr (captured at a
/Zephyr-latest/boards/ambiq/apollo3_evb/doc/
Dindex.rst52 Reset the board and you should be able to see on the corresponding Serial Port
/Zephyr-latest/boards/ambiq/apollo4p_evb/doc/
Dindex.rst53 Reset the board and you should be able to see on the corresponding Serial Port
/Zephyr-latest/boards/microchip/mec15xxevb_assy6853/doc/
Dindex.rst309 #. Final wiring for the board should look like this:
326 Under Linux the terminal should be :code:`/dev/ttyUSB0`. Do not close it.
335 string. Connection should be configured as follows:
363 #. You should see ``"Hello World! mec15xxevb_assy6853"`` in the first terminal window.
364 If you don't see this message, press the Reset button and the message should appear.
/Zephyr-latest/boards/cypress/cy8ckit_062_wifi_bt/doc/
Dindex.rst138 CM4 core working FW for both cores should be written into Flash. CM0+ FW
139 should starts the CM4 core at one point using
150 Switch the DevKit into CMSIS-DAP mode using SW3 (LED2 should blink) and flash
/Zephyr-latest/doc/kernel/data_structures/
Drbtree.rst14 anywhere in user accessible memory. It should contain only zero bits
20 A function of type :c:func:`rb_lessthan_t` should be assigned to the
22 operations are attempted. This function should, as its name suggests,
/Zephyr-latest/doc/services/pm/
Ddevice.rst37 use, and bring them back (resume) when needed. Drivers should use the
129 always active and should be suspended together with the SoC when requested by
209 pointers should be passed to ``DEVICE_DEFINE`` or ``DEVICE_DT_DEFINE``
303 operation and should not be suspended.
307 longer doing an operation and can be suspended, it should call
432 devices that should not be suspended.
/Zephyr-latest/doc/
Dzephyr.doxyfile.in14 # Values that contain spaces should be placed between quotes (\" \").
40 # double-quotes, unless you are using Doxywizard) that should identify the
54 # for a project that appears at the top of each page and should give viewer a
60 # in the documentation. The maximum height of the logo should not exceed 55
61 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
188 # the header file containing the class definition is used. Otherwise one should
351 # the files are not read by Doxygen. When specifying no_extension you should add
397 # to include (a tag file for) the STL sources as input, then you should set this
406 # If you use Microsoft's C++/CLI language, you should set this option to YES to
425 # should set this option to NO.
[all …]
/Zephyr-latest/soc/mediatek/mt8xxx/
DCMakeLists.txt33 # should live in SOF where it doesn't have to be duplicated for every
/Zephyr-latest/boards/sipeed/longan_nano/doc/
Dindex.rst61 When using a custom toolchain it should be enough to have the downloaded
/Zephyr-latest/drivers/timer/
DKconfig.stm32_lptim25 using devicetree should be preferred.
/Zephyr-latest/boards/silabs/radio_boards/xg29_rb4412a/doc/
Dindex.rst59 Reset the board and you should see the following message in the terminal:

1...<<21222324252627282930>>...51