Searched refs:and (Results 726 – 750 of 3855) sorted by relevance
1...<<21222324252627282930>>...155
| /Zephyr-latest/doc/_doxygen/ |
| D | doxygen-awesome-sidebar-only-darkmode-toggle.css | 12 of this software and associated documentation files (the "Software"), to deal
14 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
15 copies of the Software, and to permit persons to whom the Software is
18 The above copyright notice and this permission notice shall be included in all
31 @media screen and (min-width: 768px) {
|
| /Zephyr-latest/boards/realtek/rts5912_evb/doc/ |
| D | index.rst | 19 - FAN, PWM and TACHO pins
25 For more information about the evb board please see `RTS5912_EVB_Schematics`_ and `RTS5912_DATASHEE…
34 Programming and Debugging
48 #. Connect Dediprog into header ``J81`` and ``J82``.
51 #. Set the strap pin ``GPIO108`` to high and power on the board.
|
| /Zephyr-latest/boards/renode/riscv32_virtual/doc/ |
| D | index.rst | 8 ``riscv32_virtual.repl`` script and the devicetree files accordingly, this allows certain hardware
11 Programming and debugging
27 While this board is emulated and you can't "flash" it, you can use this
28 configuration to run basic Zephyr applications and kernel tests in the Renode
38 Renode, and display the following console output:
|
| /Zephyr-latest/samples/drivers/misc/grove_display/ |
| D | README.rst | 5 Display an incrementing counter and change the backlight color.
29 SCL/SDA lines and 3.3V.
31 Take note that even though SDA and SCL are connected to a 3.3V power source, the
37 Building and Running
40 This sample should work on any board that has I2C enabled and has an Arduino
|
| /Zephyr-latest/doc/develop/sca/ |
| D | cpptest.rst | 7 and static analysis tool for C and C++. It is a commercial software and you must acquire a
32 To import and generate a report file, something like the following should work.
39 You might need to set ``bdf.import.c.compiler.exec``, ``bdf.import.cpp.compiler.exec``, and
|
| /Zephyr-latest/samples/subsys/lorawan/class_a/ |
| D | README.rst | 5 Join a LoRaWAN network and send a message periodically.
12 Building and Running
21 The following commands build and flash the sample.
37 …de to increment ``join_cfg.otaa.dev_nonce`` before each connection attempt and ensure it is preser…
40 …n:`CONFIG_LORAWAN_NVM_SETTINGS` in the Kconfig. This allows proper storage and reuse of configurat…
|
| /Zephyr-latest/samples/subsys/portability/cmsis_rtos_v1/timer_synchronization/ |
| D | README.rst | 4 Use timers and message queues from CMSIS RTOS v1 API to synchronize threads.
8 The sample project illustrates usage of timers and message queues using
12 and on timer expiry, message is read by main thread.
15 Building and Running Project
17 This project outputs to the console. It can be built and executed
|
| /Zephyr-latest/samples/subsys/portability/cmsis_rtos_v2/timer_synchronization/ |
| D | README.rst | 4 Use timers and message queues from CMSIS RTOS v2 API to synchronize threads.
8 The sample project illustrates usage of timers and message queues using
12 and on timer expiry, message is read by main thread.
15 Building and Running Project
17 This project outputs to the console. It can be built and executed
|
| /Zephyr-latest/samples/shields/x_nucleo_iks4a1/sensorhub1/ |
| D | README.rst | 12 This sample enables LSM6DSV16X IMU in sensorhub mode with LIS2MDL magnetometer and
13 LPS22DF pressure and temperature sensor.
17 - LSM6DSV16X 6-Axis acceleration and angular velocity
19 - LSM6DSV16X (from LPS22DF) ambient temperature and atmospheric pressure
28 Building and Running
|
| /Zephyr-latest/samples/shields/x_nucleo_iks4a1/sensorhub2/ |
| D | README.rst | 12 This sample enables LSM6DSO16IS IMU in sensorhub mode with LIS2MDL magnetometer and
13 LPS22DF pressure and temperature sensor.
17 - LSM6DSO16IS 6-Axis acceleration and angular velocity
19 - LSM6DSO16IS (from LPS22DF) ambient temperature and atmospheric pressure
28 Building and Running
|
| /Zephyr-latest/samples/bluetooth/hci_ipc/ |
| D | README.rst | 16 * A board with IPC subsystem and Bluetooth LE support
18 Building and Running
25 and IPC support.
26 You can then build this application and flash it onto your board in
27 the usual way. See :ref:`boards` for board-specific building and
|
| /Zephyr-latest/boards/gd/gd32f403z_eval/doc/ |
| D | index.rst | 6 The GD32F403Z-EVAL board is a hardware platform that enables design and debug
11 SRAM and 112 GPIOs.
34 For more information about the GD32F403 SoC and GD32F403Z-Eval board:
52 is UART0 at PIN-9 and PIN-10.
54 Programming and Debugging
57 Before program your board make sure to configure boot setting and serial port.
59 signals between USB VBUS/ID and USART J2.
85 allow flash programming and debug over USB. There are also program and debug
86 headers J1 and J100 that can be used with any ARM compatible tools.
88 #. Build the Zephyr kernel and the :zephyr:code-sample:`hello_world` sample application:
[all …]
|
| /Zephyr-latest/boards/st/b_g474e_dpow1/doc/ |
| D | index.rst | 5 The B-G474E-DPOW1 Discovery kit is a digital power solution and a complete
6 demonstration and development platform for the STMicroelectronics STM32G474RET6
8 embedded RAM, math accelerator functions and USB-PD 3.0 offered by STM32G474RET6,
13 the STLINK-V3E debugger and programmer.
16 of Flash memory and 128 Kbytes of SRAM, in LQFP64 package
19 - Digital power buck-boost converter with internal or external Input voltage and
23 - 3 LEDs for power and ST-LINK communication
32 Virtual COM port, and debug port
48 Connections and IOs
76 Programming and Debugging
[all …]
|
| /Zephyr-latest/boards/st/nucleo_f334r8/doc/ |
| D | index.rst | 5 STM32 Nucleo-64 development board with STM32F334R8 MCU, supports Arduino and ST morpho connectivity.
7 The STM32 Nucleo board provides an affordable and flexible way for users to try out new concepts,
8 and build prototypes with the STM32 microcontroller, choosing from the various
9 combinations of performance, power consumption and features.
11 The Arduino* Uno V3 connectivity support and the ST morpho headers allow easy functionality
16 debugger and programmer.
46 - Two push-buttons: USER and RESET
63 Connections and IOs
91 Programming and Debugging
96 Applications for the ``nucleo_f334r8`` board configuration can be built and
[all …]
|
| /Zephyr-latest/doc/services/storage/disk/ |
| D | access.rst | 15 API provides IOCTLs to initialize and de-initialize the disk. They are
36 de-initialization and initialization calls should be left to the filesystem
37 implementation, and the user application should not need to manually
38 de-initialize the disk and can instead call :c:func:`fs_unmount`
43 Zephyr has support for some SD card controllers and support for interfacing
44 SD cards via SPI. These drivers use disk driver interface and a file system
46 Both standard and high-capacity SD cards are supported.
66 interface. Example uses pin ``PA27`` for chip select, and runs the SPI bus
88 The SD card will be automatically detected and initialized by the
91 To read and write files and directories, see the :ref:`file_system_api` in
[all …]
|
| /Zephyr-latest/boards/others/black_f407zg_pro/doc/ |
| D | index.rst | 7 with a wide range of connectivity support and configurations. There are
13 board and easy probing
24 - Four push-buttons: RESET, K0, K1 and WK_UP
29 power this board through USB and an external power supply at
61 - USB 2.0 OTG HS/FS with dedicated DMA, on-chip full-speed PHY and ULPI
69 - Micro USB for power and comms
85 simultaneous use of CAN_1 and CAN_2 is not yet supported.
131 In order to enable console output you should use a serial cable and connect
135 Programming and Debugging
138 Applications for the ``black_f407zg_pro`` board configuration can be built and
[all …]
|
| /Zephyr-latest/boards/gd/gd32e103v_eval/doc/ |
| D | index.rst | 6 The GD32E103V-EVAL board is a hardware platform that enables design and debug
11 SRAM and 80 GPIOs.
34 For more information about the GD32E103 SoC and GD32E103V-EVAL board:
52 is UART0 at PIN-9 and PIN-10.
54 Programming and Debugging
57 Before program your board make sure to configure boot setting and serial port.
59 signals between USB VBUS/ID and USART J2.
85 allow flash programming and debug over USB. There are also program and debug
86 headers J1 and J100 that can be used with any ARM compatible tools.
88 #. Build the Zephyr kernel and the :zephyr:code-sample:`hello_world` sample application:
[all …]
|
| /Zephyr-latest/samples/modules/chre/ |
| D | README.rst | 21 #. *GNSS* - a framework allowing nanoapps to manage location and measurement sessions. See
26 and some basic memory allocation/deallocation. See `pal/system.h`_ for API details.
30 current capabilities and info. See `pal/wwan.h`_ for API details.
32 Building and expectations
42 Once built and run, the sample application should:
46 #. Notify that a nanoapp was started and assigned an instance/app ID of 1 via a ``dbg`` level log
48 #. Send an event of type ``1`` and no data to the nanoapp
57 #. Add an implementation of the `pal/sensor.h`_ and `pal/system.h`_ to Zephyr. These will be
59 will also provide an implementation of ``chrePalSensorGetApi()`` and ``struct chrePalSystemApi``.
61 community. These should each have their own Kconfig to enable them and set the appropriate
[all …]
|
| /Zephyr-latest/samples/boards/nordic/mesh/onoff_level_lighting_vnd_app/ |
| D | README.rst | 47 * Button1 and Button2 are associated with gen. OnOff Client or Vendor Model which is part of Root e…
48 * Button3 and Button4 are associated with gen. Level Client / Light Lightness Client / Light CTL Cl…
53 be configured to publish and the LED servers to subscribe.
62 Building and Running
77 - Button1, Button2, and LED1 to application key 1. It then configures Button1 and Button2
78 to publish to group 0xC000 and LED1 to subscribe to that group.
79 - Button3, Button4, and LED3 to application key 1. It then configures Button3 and Button4
80 to publish to group 0xC000 and LED3 to subscribe to that group.
105 meshctl is gracefully exited, it can be restarted and reconnected to
111 that has that LED's model and issuing the onoff command.
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.cavs | 9 # Zephyr's perspective is the framework and also the application.
11 # option and remove it.
27 external oscillator and is external to the CPU core(s).
29 a common and synchronized counter for all CPU cores (which
|
| /Zephyr-latest/doc/services/debugging/ |
| D | symtab.rst | 7 stage that keep tracks of the information about the functions' name and address, for advanced appli…
17 file and call :c:func:`symtab_get`. For now, we only provide :c:func:`symtab_find_symbol_name`
18 function to look-up the symbol name and offset of an address. More advanced functionalities and be
|
| /Zephyr-latest/soc/snps/emsk/ |
| D | linker.ld | 14 * DRAM base address and size
25 /* Instruction Closely Coupled Memory (ICCM) base address and size */
33 * DCCM base address and size. DCCM is the data memory.
35 /* Data Closely Coupled Memory (DCCM) base address and size */
|
| /Zephyr-latest/samples/sensor/ams_iAQcore/ |
| D | README.rst | 5 Get CO2 equivalent and VOC data from an ams iAQcore sensor.
11 measure CO2 equivalent and VOC. The CO2 value is a predicted value derived from
12 VOC. The values are fetched and printed every second.
14 Building and Running
|
| /Zephyr-latest/samples/sensor/ms5837/ |
| D | README.rst | 5 Get pressure and temperature data from an MS5837 sensor (polling mode).
10 This sample application retrieves the pressure and temperature from a MS5837
11 sensor every 10 seconds, and prints this information to the UART console.
34 Building and Running
|
| /Zephyr-latest/doc/develop/debug/ |
| D | index.rst | 13 `QEMU`_ and `GNU_Debugger`_ reference manuals.
20 variables, and parameters that can help you to quickly set up your debugging
24 Debugger and setting a local GDB server in your development system through QEMU.
26 You will need an :abbr:`ELF (Executable and Linkable Format)` binary image for
37 QEMU instance with the processor halted at startup and with a GDB server
50 will setup Qemu to listen on port 1234 and wait for a GDB connection to it.
91 device. GDB releases 9.0 and newer also support Unix domain sockets.
100 Connect to the server by running :command:`gdb` and giving these commands:
147 change depending on the toolchain you are using and your cross-development
176 the Eclipse Integrated Development Environment (IDE) and used for graphical
[all …]
|
1...<<21222324252627282930>>...155
