Searched refs:can (Results 326 – 350 of 2493) sorted by relevance
1...<<11121314151617181920>>...100
/Zephyr-latest/doc/services/storage/stream/ |
D | stream_flash.rst | 23 When performing such long running operations it can be useful to be able to save 24 the stream write progress to persistent storage so that the operation can resume 29 module. The API can be enabled using :kconfig:option:`CONFIG_STREAM_FLASH_PROGRESS`.
|
/Zephyr-latest/doc/kernel/services/other/ |
D | thread_local_storage.rst | 23 :kconfig:option:`CONFIG_ERRNO_IN_TLS` can be enabled together with 32 The macro ``Z_THREAD_LOCAL`` can be used to declare thread local variables. 46 Keyword ``static`` can also be used to limit the variable within a source file:
|
/Zephyr-latest/boards/bbc/microbit/doc/ |
D | index.rst | 12 25 LEDs, two programmable buttons, and can be powered by either USB or an 16 More information about the board can be found at the `microbit website`_. 55 can be found. For example, under Linux, :code:`/dev/ttyACM0`.
|
/Zephyr-latest/boards/vngiotlab/nrf52_vbluno52/doc/ |
D | index.rst | 6 Zephyr can use the nrf52_vbluno52 board configuration to run on the VBLUno52 board, 56 You can build and flash applications in the usual way. Here is an 67 Here are some sample applications that you can use to test different
|
/Zephyr-latest/samples/drivers/mbox/ |
D | README.rst | 15 The sample can be built and executed on boards supporting MBOX. 74 Then you can execute your application using: 81 You can expect a similar output as in the real HW in the invoking console.
|
/Zephyr-latest/boards/ezurio/bt610/doc/ |
D | bt610.rst | 34 More information about the board can be found at the 57 Two LEDs are visible through the BT610 housing lid. Note that the LEDs can be 106 This can deliver up to 50mA peak and 20mA continuous current. 204 Signals up to 12V, to a maximum of 50mA, can be applied to the external Analog 276 Circuitry associated with the analog input measurements can be disabled when 314 The table below defines possible values that can be written. 348 must first be set. This approach is taken to ensure supporting circuitry can be 350 external digital input level can be read from the appropriate input pin. 384 Power can be supplied to external sensors via the B+ OUT terminal. This is 386 external supply can be boosted to 5V by setting the HIGH_SUPPLY_ENABLE GPIO [all …]
|
/Zephyr-latest/boards/shields/npm6001_ek/doc/ |
D | index.rst | 30 The shield can be used in any application by setting ``--shield npm6001_ek`` 31 when invoking ``west build``. You can check :zephyr:code-sample:`npm6001_ek` for a
|
/Zephyr-latest/soc/st/stm32/stm32u5x/ |
D | Kconfig | 32 SRAMs can be totally or partially switched off to further reduce consumption. 33 GPIOs are left floating and additional pull-up or pull-down can be applied
|
/Zephyr-latest/tests/arch/arm/arm_sw_vector_relay/ |
D | README.txt | 13 This project outputs to the console. It can be built and executed on QEMU as 22 Problems caused by out-dated project information can be addressed by
|
/Zephyr-latest/samples/boards/nordic/system_off/ |
D | README.rst | 10 This sample can be used for basic power measurement and as an example of 16 This sample can also demonstrate RAM retention.
|
/Zephyr-latest/boards/raspberrypi/rpi_pico/doc/ |
D | index.rst | 58 The peripherals of the RP2040 SoC can be routed to various pins on the board. 59 The configuration of these routes can be modified through DTS. Please refer to 98 can be found at :zephyr_file:`drivers/serial/uart_rpi_pico_pio.c`. 115 Raspberry Pi Pico's PIO is a programmable chip that can implement a variety of peripherals. 136 Applications for the ``rpi_pico`` board configuration can be built and 165 It can be used with 175 can also be used. 181 The ``rpi_pico`` can flash with Zephyr's standard method. 204 The Raspberry Pi Pico has an SWD interface that can be used to program 205 and debug the onboard SoC. This interface can be used with OpenOCD. [all …]
|
/Zephyr-latest/doc/kernel/memory_management/ |
D | demand_paging.rst | 26 and execution can continue. 28 There are functions where paging in and out can be invoked manually 30 :c:func:`k_mem_page_in()` can be used to page in data pages 33 memory, and thus minimizing latency. :c:func:`k_mem_page_out()` can be 36 page in can be executed faster as the paging code does not need to invoke 44 or be paged out to some backing store. Its location can always be looked 90 Paging statistics can be obtained via various function calls when 98 * Execution time histogram can be obtained when 120 corresponding page frame can be paged out to free up a page frame 177 reserve a backing store location so a data page can be paged out. [all …]
|
D | slabs.rst | 19 Any number of memory slabs can be defined (limited only by available RAM). Each 38 A memory slab must be initialized before it can be used. This marks all of 43 it must release the block back to the memory slab so the block can be reused. 45 If all the blocks are currently in use, a thread can optionally wait 51 Unlike a heap, more than one memory slab can be defined, if needed. This 83 Alternatively, a memory slab can be defined and initialized at compile time 93 Similarly, you can define a memory slab in private scope:
|
/Zephyr-latest/doc/services/mem_mgmt/ |
D | index.rst | 8 region can then be retrieved at run-time by leveraging a provided helper 11 The set of general attributes that can be specified in the property are defined 33 The ``zephyr,memory-attr`` property can also be used to set 34 architecture-specific and software-specific custom attributes that can be 56 array and a set of functions is made available that can be used to query, probe 80 The developers that are still using the deprecated property can move to the new 96 to define and create a set of memory heaps from which the user can allocate 113 For example we can define several memory regions with different attributes and 144 The user can then dynamically carve memory out of those regions using the 192 MMU (if needed) and that an actual heap can be created out of it, for
|
/Zephyr-latest/doc/kernel/ |
D | code-relocation.rst | 17 A regular expression filter can be used to select only the required sections to be relocated. 72 function zephyr_code_relocate() can be called as many times as required. 76 This section shows additional configuration options that can be set in 96 * Multiple regions can also be appended together such as: SRAM2_DATA_BSS. 99 * Multiple files can be passed to the FILES argument, or CMake generator 100 expressions can be used to relocate a comma-separated list of files 115 The regular expression applies to sections names which can be used to 133 you can pass ``NOKEEP`` to your ``zephyr_code_relocate()`` call. 146 the relocation code is not generated in ``code_relocation.c``. This flag can be 162 Libraries can be relocated using the LIBRARY argument to
|
/Zephyr-latest/doc/project/ |
D | proposals.rst | 41 A feature request can also have a companion RFC with more details on the feature 58 assignee are open for grabs, meaning that they can be picked up and implemented 83 If built properly, the roadmap can be a valuable tool for several reasons. It 84 can help the project present its plan in a compelling way to existing and new 85 stakeholders, to help recruit new members and it can be a helpful resource the 86 team and community can refer to throughout the project's development, to ensure 103 and main stakeholders of the project can make progress on.
|
/Zephyr-latest/boards/native/nrf_bsim/doc/ |
D | nrf5340bsim.rst | 70 can use the corresponding simulated target, nrf5340bsim/nrf5340/cpuapp or nrf5340bsim/nrf5340/cpunet 78 developing without an image in the application core. You can control 96 you can provide that image to the Zephyr build of the second image using 99 You can also use :ref:`System build (sysbuild) <sysbuild>` to build your dual MCU executable. 117 own interconnect master ports can, in principle, access any other peripheral or RAM area. 121 can be labelled as restricted for secure or non secure access. 124 Note that the ARM cryptocell-312 peripheral is not modelled. The mbedTLS library can still be used
|
/Zephyr-latest/boards/st/nucleo_f446re/doc/ |
D | index.rst | 25 More information about the board can be found at the `Nucleo F446RE website`_. 57 More information about STM32F446RE can be found here: 122 In order to test backup SRAM you may want to disconnect VBAT from VDD. You can 128 The TX/RX wires connected with D14/D15 of CN5 connector. Thus the board can be 136 Applications for the ``nucleo_f446re`` board configuration can be built and 146 Alternatively, OpenOCD or JLink can also be used to flash the board using 181 You can debug an application in the usual way. Here is an example for the
|
/Zephyr-latest/boards/st/nucleo_g0b1re/doc/ |
D | index.rst | 28 More information about the board can be found at the `Nucleo G0B1RE website`_. 61 More information about STM32G0B1RE can be found here: 75 Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as 105 Applications for the ``nucleo_g0b1re`` board configuration can be built and 115 Alternatively, OpenOCD, JLink, or pyOCD can also be used to flash the board using 125 which can be installed by adding "pack" support with the following pyocd command: 147 You can debug an application in the usual way. Here is an example for the
|
/Zephyr-latest/doc/connectivity/networking/ |
D | native_sim_setup.rst | 24 On the Linux Host, find the Zephyr `net-tools`_ project, which can either be 57 You can tweak the behavior of the net-setup.sh script. See various options 84 started but if it does not show up, you can manually connect to the console. 91 You can manually connect to it like this: 120 On the Linux Host, find the Zephyr `net-tools`_ project, which can either be 155 The same applies to the IPv4 address, gateway and netmask. They can be set 164 This can be useful if the application has to be
|
/Zephyr-latest/tests/subsys/logging/log_blocking/ |
D | REAME.md | 5 When the core log buffer becomes full, the logging subsystem can be configured to 20 `CONFIG_LOG_BLOCK_IN_THREAD`, and they can all be characterized by comparing 36 Rate-limiting of any kind can be described approximately as _back pressure_. 37 Back pressure is fine in short bursts but it can cause delays in application 45 DMA, can provide significantly higher throughput but are still inherently 50 memory or the CPU. From that perspective, we can infer that there is a finite 58 stall. We can also be sure that the output will be able to relieve
|
/Zephyr-latest/boards/intel/socfpga/agilex5_socdk/doc/ |
D | index.rst | 47 The default configuration can be found in the defconfig file: 62 Intel Arm Trusted Firmware (ATF) can be downloaded from github: 67 Zephyr image can be loaded in DDR memory at address 0x80000000 from 75 Zephyr applications running on the Cortex-A55/A76 core can be tested by
|
/Zephyr-latest/boards/nxp/ucans32k1sic/ |
D | ucans32k1sic.dts | 86 can_phy0: can-phy0 { 87 compatible = "nxp,tja1463", "nxp,tja1443", "nxp,tja1153", "can-transceiver-gpio"; 93 can_phy1: can-phy1 { 94 compatible = "nxp,tja1463", "nxp,tja1443", "nxp,tja1153", "can-transceiver-gpio";
|
/Zephyr-latest/boards/renesas/ek_ra2a1/doc/ |
D | index.rst | 34 Detail Hardware feature for the RA2A1 MCU group can be found at `RA2A1 Group User's Manual Hardware… 43 Detail Hardware feature for the EK-RA2A1 MCU can be found at `EK-RA2A1 - User's Manual`_ 66 You can build and flash an application with onboard J-Link debug adapter. 81 Debugging also can be done with onboard J-Link debug adapter.
|
/Zephyr-latest/doc/contribute/style/ |
D | index.rst | 61 issues, you can add option --no-verify to the git push command. 69 The `clang-format tool <https://clang.llvm.org/docs/ClangFormat.html>`_ can 73 editors, but you can also run it manually like this: 79 ``clang-format`` is part of LLVM, which can be downloaded from the project
|
1...<<11121314151617181920>>...100