Home
last modified time | relevance | path

Searched refs:step (Results 126 – 150 of 210) sorted by relevance

123456789

/Zephyr-latest/boards/st/nucleo_l496zg/doc/
Dindex.rst48 - LCD 8 x 40 or 4 x 44 with step-up converter
/Zephyr-latest/boards/st/nucleo_l4a6zg/doc/
Dindex.rst48 - LCD 8 x 40 or 4 x 44 with step-up converter
/Zephyr-latest/boards/ezurio/bt510/doc/
Dbt510.rst212 :ref:`nordic_segger` page also apply to this board, with the additional step
/Zephyr-latest/boards/olimex/olimex_esp32_evb/doc/
Dindex.rst12 LiPo battery charger. There is no step-up converter, so relays, CAN, and USB
/Zephyr-latest/boards/nxp/mimxrt1020_evk/doc/
Dindex.rst282 Open a serial terminal, step through the application in your debugger, and you
/Zephyr-latest/samples/subsys/mgmt/updatehub/
DREADME.rst357 menu, then ``UPLOAD PACKAGE``, and select the package built in step 8.
389 in step 9. With that, the update is published, and the server is ready to
/Zephyr-latest/doc/build/
Dzephyr_cmake_package.rst349 file is found, go to step 2.
353 It is recommended to place the files in the default paths from step 2, but with the
/Zephyr-latest/drivers/sensor/nordic/npm1300_charger/
Dnpm1300_charger.c556 config->current_microamp - charger_current_range.step, in npm1300_charger_init()
/Zephyr-latest/doc/develop/west/
Dtroubleshooting.rst200 this step.)
/Zephyr-latest/cmake/
Dmcuboot.cmake7 # It builds signed binaries using imgtool as a post-processing step
/Zephyr-latest/doc/services/device_mgmt/
Dmcumgr_handlers.rst21 to reside in the upstream Zephyr tree to be usable. The first step to creating a handler is to
/Zephyr-latest/boards/st/stm32l496g_disco/doc/
Dindex.rst64 - LCD 8 x 40 or 4 x 44 with step-up converter
/Zephyr-latest/boards/st/stm32u083c_dk/doc/
Dindex.rst132 - 8*48 or 4*52 segments, with step-up converter
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dprovisioning.rst25 Provisioning is a five-step process, involving the following steps:
/Zephyr-latest/tests/bsim/bluetooth/audio/src/
Dvcp_vol_rend_test.c774 vcp_register_param.step = 1; in test_register()
/Zephyr-latest/boards/nxp/imx8mm_evk/doc/
Dindex.rst240 Open a serial terminal, step through the application in your debugger, and you
/Zephyr-latest/boards/nxp/mimxrt1062_fmurt6/doc/
Dindex.rst324 Open a serial terminal, step through the application in your debugger, and you
/Zephyr-latest/boards/nxp/vmu_rt1170/doc/
Dindex.rst527 Open a serial terminal, step through the application in your debugger, and you
/Zephyr-latest/boards/nxp/frdm_k82f/doc/
Dindex.rst215 Open a serial terminal, step through the application in your debugger, and you
/Zephyr-latest/boards/nxp/frdm_mcxn947/doc/
Dindex.rst256 Open a serial terminal, step through the application in your debugger, and you
/Zephyr-latest/samples/subsys/mgmt/hawkbit/
DREADME.rst121 The easiest way to test the functionality of hawkBit is to repeat step 4 to
/Zephyr-latest/doc/releases/
Drelease-notes-4.1.rst249 …* Added :kconfig:option:`CONFIG_STEP_DIR_STEPPER` to enable common functions for step/dir steppers.
/Zephyr-latest/boards/st/stm32h7s78_dk/doc/
Dindex.rst87 - Embedded SMPS step-down converter
/Zephyr-latest/boards/toradex/verdin_imx8mm/doc/
Dindex.rst246 Open a serial terminal, step through the application in your debugger, and you
/Zephyr-latest/boards/st/nucleo_u575zi_q/doc/
Dindex.rst71 - Embedded SMPS step-down converter supporting switch on-the-fly and voltage scaling

123456789