Home
last modified time | relevance | path

Searched refs:should (Results 326 – 350 of 1262) sorted by relevance

1...<<11121314151617181920>>...51

/Zephyr-latest/boards/silabs/dev_kits/xg24_ek2703a/doc/
Dindex.rst75 Before using the kit the first time, you should update the J-Link firmware
90 should see a USB connection.
/Zephyr-latest/drivers/timer/
DKconfig.x8650 logic). SMP-safe and very fast, this should be the obvious
79 user-configurable and almost certainly should be managed via
DKconfig.riscv_machine32 The division ratio should define in devicetree,
/Zephyr-latest/boards/sc/scobc_module1/doc/
Dindex.rst75 After flashing, you should see message similar to the following in the terminal:
95 Step through the application in your debugger, and you should see a message
/Zephyr-latest/doc/kernel/usermode/
Dmpu_stack_objects.rst48 This means that a 1500 byte stack should be aligned to a 2kB boundary and the
49 stack size should also be adjusted to 2kB to ensure that nothing else is
/Zephyr-latest/arch/
DKconfig187 Little-endian architecture is the default and should leave this option
189 soc/**/Kconfig, or boards/**/Kconfig and the user should generally avoid
208 soc/**/Kconfig, or boards/**/Kconfig and the user should generally
219 devicetree. The user should generally avoid changing it via menuconfig or
227 /chosen/zephyr,sram in devicetree. The user should generally avoid
241 the board's defconfig file and the user should generally avoid modifying
250 normally set by the board's defconfig file and the user should generally
367 FIXME: This should be removed and replaced with checks against
797 This hidden configuration should be selected by the architecture if
803 This hidden configuration should be selected by the architecture if
[all …]
/Zephyr-latest/boards/silabs/dev_kits/sltb004a/doc/
Dindex.rst112 Before using the kit the first time, you should update the J-Link firmware
138 should see a USB connection which exposes a Mass Storage (TB004) and a
148 Reset the board and you should be able to see on the corresponding Serial Port
/Zephyr-latest/arch/arm/core/
DKconfig.vfp6 # Math coprocessor symbols; these should be selected by the CPU symbol to
25 # VFP type symbols; these should be selected by the SoC symbol to specify the
197 # Advanced SIMD type symbols; these should be selected by the SoC symbol to
/Zephyr-latest/boards/atmel/sam0/samr21_xpro/doc/
Dindex.rst156 terminal should be :code:`/dev/ttyACM0`. For example:
163 string. Connection should be configured as follows:
178 You should see "Hello World! samr21_xpro" in your terminal.
/Zephyr-latest/boards/adafruit/feather_m4_express/doc/
Dindex.rst100 terminal should be :code:`/dev/ttyUSB0`. For example:
107 string. Connection should be configured as follows:
124 You should see "Hello World! adafruit_feather_m4_express" in your terminal.
/Zephyr-latest/drivers/serial/
DKconfig.xen35 Set init priority for Xen HVC, should be inited before UART
/Zephyr-latest/cmake/
Dverify-toolchain.cmake23 # all other messages as only the specified output should be printed.
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dop_agg_srv.rst19 The targeted server models should be bound to the same application key that is used
/Zephyr-latest/samples/drivers/misc/ft800/
DREADME.rst30 This sample should work on any board that has SPI enabled and has an Arduino
/Zephyr-latest/samples/drivers/stepper/tmc50xx/
DREADME.rst29 driver. It should work with any platform featuring a SPI peripheral interface.
/Zephyr-latest/samples/drivers/uart/echo_bot/
DREADME.rst19 is used, so that almost every board should be supported.
/Zephyr-latest/include/zephyr/linker/
Dintlist.ld25 * shouldn't overlap any other regions. On most arches the following should be
/Zephyr-latest/tests/drivers/build_all/video/
Dmimxrt1170_evk_mimxrt1176_cm7.overlay6 * Names in this file should be chosen in a way that won't conflict
/Zephyr-latest/samples/drivers/led/lp3943/
DREADME.rst36 When you connect to the board's serial console, you should see the
/Zephyr-latest/samples/boards/st/backup_sram/
DREADME.rst40 Next reported value should be: 12
/Zephyr-latest/samples/subsys/task_wdt/
DREADME.rst15 It should be possible to build and run the task watchdog sample on almost any
/Zephyr-latest/samples/sensor/grove_light/
DREADME.rst27 overlay provided for the sample, the sensor should be connected to A0 on the Grove shield.
/Zephyr-latest/boards/altr/max10/doc/
Dindex.rst18 * Switch 2 (CONFIG_SEL) should be in the OFF (up) position so that the first
22 * Switch 4 (HSMC_BYPASSN) should be OFF (up)
38 you should put the binaries provided by the SDK
70 You can test connectivity with the SDK jtagconfig tool, you should see something
178 should see the application's output. There are additional arguments you can pass
267 any) is on the device, but you should have at least flashed a CPU using
/Zephyr-latest/modules/
DKconfig.mcuboot55 This option should contain a path to the same file as the
86 This option should either be an absolute path or a path relative to
158 MCUBOOT_BOOTLOADER_NO_DOWNGRADE should also be selected
167 MCUBOOT_BOOTLOADER_NO_DOWNGRADE should also be selected
186 MCUBOOT_BOOTLOADER_NO_DOWNGRADE should also be selected
271 This options should be selected when MCUboot has been built with
282 Note that the zephyr chosen node ``zephyr,code-partition`` should be set to
/Zephyr-latest/doc/services/smf/
Dindex.rst89 To set the initial state, the :c:func:`smf_set_initial` function should be
96 :c:func:`smf_set_initial` and :c:func:`smf_set_state` function should
100 HSM should have initial transitions defined for all parent states.
102 .. note:: While the state machine is running, :c:func:`smf_set_state` should
110 To run the state machine, the :c:func:`smf_run_state` function should be
111 called in some application dependent way. An application should cease calling
125 should be called. It can be called from the entry, run, or exit actions. The
361 When designing hierarchical state machines, the following should be considered:

1...<<11121314151617181920>>...51