Searched refs:and (Results 376 – 400 of 3855) sorted by relevance
1...<<11121314151617181920>>...155
| /Zephyr-latest/boards/u-blox/ubx_bmd340eval/doc/ |
| D | index.rst | 3 u-blox EVK-BMD-34/38: BMD-340-EVAL and BMD-341-EVAL
9 The BMD-340-EVAL and BMD-341-EVAL hardware provides support for the
10 u-blox BMD-340 and BMD-341 Bluetooth 5.0 modules, based on the
11 Nordic Semiconductor nRF52840 ARM Cortex-M4F CPU. the BMD-340 and
24 * RADIO (Bluetooth Low Energy and 802.15.4)
39 and BMD-341 module can be found at the `u-blox website`_.
44 The BMD-340 and BMD-341 are identical except for the antenna.
54 The BMD-340 and BMD-341 do not include the slow crystal;
55 however, the BMD-340-EVAL and BMD-341-EVAL do.
66 The BMD-340-EVAL and BMD-341-EVAL board configuration supports
[all …]
|
| /Zephyr-latest/doc/build/dts/ |
| D | intro.rst | 8 This is a conceptual overview of devicetree and how Zephyr uses it. For
9 step-by-step guides and examples, see :ref:`dt-howtos`.
11 The following pages introduce general devicetree concepts and how they apply to
|
| /Zephyr-latest/drivers/mfd/ |
| D | Kconfig.lpflexcomm | 11 LP FLexcomm allows enablement of LPUART and LPI2C
13 checks concurrent enablement and returns and error for
|
| /Zephyr-latest/tests/lib/cbprintf_fp/ |
| D | README.txt | 1 Footprint and Behavior Test for cbprintf variants
5 minimal libc and newlib versions with printk, printf, and cbprintf.
|
| /Zephyr-latest/boards/sparkfun/micromod/doc/ |
| D | index.rst | 10 to mix and match your choice of processor with specific Function Boards or
12 and can insert into any MicroMod carrier board. More information can be found in
44 a powerful combination of ARM Cortex-M4 CPU and 2.4 GHz Bluetooth transceiver
59 - Integrated 2.4GHz radio with support for Bluetooth Low Energy (BLE) and ieee802154
106 Connections and IOs
124 Programming and Debugging
128 built, flashed, and debugged in the usual way. See
129 :ref:`build_an_application` and :ref:`application_run` for more details on
130 building and running.
136 and configure all the necessary software. Further information can be
[all …]
|
| /Zephyr-latest/boards/phytec/phyboard_nash/doc/ |
| D | index.rst | 10 SoC. It features common industrial interfaces and can be used as a reference for
15 i.MX93 MPU is composed of one cluster of 2x Cortex-A55 cores and a single
41 - USB-C for UART debug, 2x serial ports for A55 and M33
104 CPU's UART2 for A55 core and M33 core. The u-boot bootloader or Linux use the
107 Programming and Debugging (A55)
110 Copy the compiled ``zephyr.bin`` to the ``BOOT`` partition of the SD card and
111 plug the SD card into the board. Power it up and stop the u-boot execution at
114 Use U-Boot to load and execute zephyr.bin on Cortex-A55 Core0:
121 Use this configuration to run basic Zephyr applications and kernel tests,
136 Programming and Debugging (M33)
[all …]
|
| /Zephyr-latest/boards/waveshare/nrf51_ble400/doc/ |
| D | index.rst | 17 - LEDs and user keys, compatible with other official boards, easy to use
27 - Expansion pinheader: all the I/Os except P0.26 and P0.27
42 - Independent application development and protocol stack
54 In June of 2015, Core51822 and its variant, Core51822 (B), upgraded the onboard chip to Rev3 (nRF51…
63 Connections and IOs
103 Connections and IOs
156 Programming and Debugging
163 and configure all the necessary software. Further information can be
164 found in :ref:`nordic_segger_flashing`. Then build and flash
165 applications as usual (see :ref:`build_an_application` and
[all …]
|
| /Zephyr-latest/boards/nxp/mcxw72_evk/doc/ |
| D | index.rst | 9 multiprotocol radio subsystem supporting Matter, Thread, Zigbee and
10 Bluetooth LE. The independent radio subsystem, with a dedicated core and
11 memory, offloads the main CPU, preserving it for the primary application and
22 For more information about the MCXW72 SoC and MCXW72-EVK board, see:
69 Programming and Debugging
72 Build and flash applications as usual (see :ref:`build_an_application` and
78 A debug probe is used for both flashing and debugging the board. This board is
84 Linkserver is the default runner for this board, and supports the factory
110 Connect a USB cable from your PC to J14, and use the serial terminal of your choice
128 Open a serial terminal, reset the board (press the RESET button), and you should
[all …]
|
| /Zephyr-latest/boards/native/nrf_bsim/doc/ |
| D | nrf5340bsim.rst | 16 ``nrf5340bsim/nrf5340/cpuapp`` and ``nrf5340bsim/nrf5340/cpunet``.
18 These use `BabbleSim`_ to simulate the radio activity, and the
19 :ref:`POSIX architecture<Posix arch>` and the `native simulator`_ to
21 providing native code execution performance and easy debugging using
26 and the nrf5340bsim/nrf5340/cpunet build target provides support for the network
49 and will use the same drivers as the nrf5340dk targets for these.
53 Note that unlike a real nrf5340 device, the nrf5340bsim boards have unlimited RAM and flash for
66 Building for, and using these boards
91 to that MCU code image, and an executable (``zephyr/zephyr.exe``) that includes the native simulator
92 runner, SOC HW models, that image, and an empty image for the other MCU.
[all …]
|
| /Zephyr-latest/doc/develop/languages/c/ |
| D | index.rst | 9 Zephyr is primarily written in C and natively supports applications written in
10 the C language. All Zephyr API functions and macros are implemented in C and
29 toolchain that supports the C99 standard and above:
42 processor for Zephyr, makes use of the C11 type-generic expressions, and this
44 toolchain that supports the C11 standard and above.
48 note that some optional Zephyr components and external modules may make use of
58 The `C Standard Library`_ is an integral part of any C program, and Zephyr
78 C defines standard formatted output functions such as ``printf`` and
79 ``sprintf`` and these functions are implemented by the C standard
82 Each C standard library has its own set of requirements and configurations for
[all …]
|
| /Zephyr-latest/boards/st/b_u585i_iot02a/doc/ |
| D | index.rst | 7 with a wide range of connectivity support and configurations. Here are
13 - USB FS, Sink and Source power, 2.5 W power capability
19 - Relative humidity and temperature sensor
21 - 3D accelerometer and 3D gyroscope
23 - Time-of-flight and gesture-detection sensor
26 - 2 push-buttons (user and reset)
44 - Ultra-low-power with FlexPowerControl (down to 300 nA Standby mode and 19.5 uA/MHz run mode)
45 - Core: ARM |reg| 32-bit Cortex |reg| -M33 CPU with TrustZone |reg| and FPU.
51 - Security and cryptography
53 - Arm |reg| TrustZone |reg| and securable I/Os memories and peripherals
[all …]
|
| /Zephyr-latest/boards/beagle/beaglebone_ai64/ |
| D | beaglebone_ai64_j721e_main_r5f0_0-pinctrl.dtsi | 13 /* 0x1c is address of padconfig register of p8.34 and 14 is mux mode */
18 /* 0x14 is address of padconfig register of p8.22 and 14 is mux mode */
22 /* 0x1e0 is the address of padconfig register of p9.17 and 2 is mux mode */
26 /* 0x1dc is the address of padconfig register of p9.18 and 2 is mux mode */
|
| /Zephyr-latest/boards/wiznet/w5500_evb_pico/doc/ |
| D | index.rst | 7 Pi RP2040 and fully hardwired TCP/IP controller W5500 - and basically works
10 drag-and-drop manner. It is also possible to flash and debug the boards with
45 (P16-P19), with the reset and interrupt signal for the W5500 routed to P20 and
49 Refer to `W55500 Evaluation Board Documentation`_ for a board schematic and
74 Programming and Debugging
84 :ref:`Building, Flashing and Debugging <west-flashing>`.
86 Here is an example of building and flashing the :zephyr:code-sample:`blinky` application.
102 Create a file in /etc/udev.rules.d with any name, and write the line below.
110 The Raspberry Pi Pico, and thus the W55500 Evaluation Board, has an SWD
111 interface that can be used to program and debug the on board RP2040. This
[all …]
|
| /Zephyr-latest/boards/st/nucleo_u575zi_q/doc/ |
| D | index.rst | 7 provides an affordable and flexible way for users to try out new concepts and
8 build prototypes by choosing from the various combinations of performance and
27 - Two push-buttons: USER and RESET
37 - Ultra-low-power with FlexPowerControl (down to 300 nA Standby mode and 19.5 uA/MHz run mode)
38 - Core: ARM |reg| 32-bit Cortex |reg| -M33 CPU with TrustZone |reg| and FPU.
46 - Arm |reg| TrustZone |reg| and securable I/Os memories and peripherals
47 - Flexible life cycle scheme with RDP (readout protection) and password protected debug
48 - Root of trust thanks to unique boot entry and secure hide protection area (HDP)
71 - Embedded SMPS step-down converter supporting switch on-the-fly and voltage scaling
73 - RTC with HW calendar and calibration
[all …]
|
| /Zephyr-latest/boards/silabs/ |
| D | index.rst | 15 number (OPN) of the kit, as found on the packaging and on the Silicon Labs
17 and replacing dashes with underscores.
19 You may find multiple other number and letter sequences silk-screened or lasered
20 onto Silicon Labs boards, including a PCB* number and a BRD* number. In most
24 use the ``west boards`` command to search for board names if you have a PCB and
|
| /Zephyr-latest/soc/snps/nsim/arc_classic/ |
| D | linker.ld | 13 /* Instruction Closely Coupled Memory (ICCM) base address and size */
21 * DCCM base address and size. DCCM is the data memory.
23 /* Data Closely Coupled Memory (DCCM) base address and size */
30 /* SRAM - memory available for all cores in cluster. Can be used for both instructions and data */
36 /* Flash memory base address and size */
|
| /Zephyr-latest/boards/makerdiary/nrf52840_mdk/doc/ |
| D | index.rst | 7 Bluetooth 5, Bluetooth Mesh, Thread, IEEE 802.15.4, ANT and 2.4GHz proprietary
11 DAPLink) that provides USB drag-and-drop programming, USB Virtual COM port
12 and CMSIS-DAP interface.
15 ports: one for DAPLink interface and one for nRF52840 USB device controller.
20 board and `nRF52840 website`_ for the official reference on the IC itself.
|
| /Zephyr-latest/tests/kernel/sleep/ |
| D | README.txt | 1 Title: cooperative thread Sleep and Wakeup APIs
5 This test verifies that cooperative sleep and wakeup APIs operate as
10 Building and Running Project:
12 This project outputs to the console. It can be built and executed
28 # and restore pre-defined configuration info
|
| /Zephyr-latest/samples/subsys/input/draw_touch_events/ |
| D | README.rst | 12 Building and Running
14 While this is a generic sample and it should work with any boards with both display controllers
15 and touch controllers supported by Zephyr (provided the corresponding ``/chosen node`` properties
16 are set i.e. ``zephyr,touch`` and ``zephyr,display``).
26 board is also supported and can be built as follows:
|
| /Zephyr-latest/samples/basic/fade_led/ |
| D | README.rst | 14 cycle. Each cycle takes 2.5 seconds, and the cycles repeat forever. The PWM
18 Requirements and Wiring
21 This sample has the same requirements and wiring considerations as the
24 Building and Running
27 To build and flash this sample for the :ref:`nrf52840dk_nrf52840`:
|
| /Zephyr-latest/samples/subsys/usb/mass/ |
| D | Kconfig | 12 prompt "Storage and file system type used by the application"
15 Specify the type of storage and file system.
21 bool "Use RAM disk and FAT file system"
26 bool "Use FLASH disk and FAT file system"
32 bool "Use FLASH disk and LittleFS"
38 bool "Use SDHC and FAT file system"
|
| /Zephyr-latest/boards/panasonic/panb511evb/doc/ |
| D | index.rst | 10 More information about the PAN B511 Module Variants and Evaluation Board can be found
27 and other things.
32 Programming and Debugging
36 be built, flashed, and debugged in the usual way. See
37 :ref:`build_an_application` and :ref:`application_run` for more details on
38 building and running.
|
| /Zephyr-latest/doc/services/ |
| D | notify.rst | 7 operation is initiated and the application needs to be informed when it
8 completes, and whether it succeeded. Using :c:func:`k_poll` is
10 suited to a callback notification, and operations like enabling clocks
11 and power rails may need to be invoked before kernel functions are
15 :ref:`resource_mgmt_onoff` and other APIs that support async
18 element, and for invoking callbacks with the parameters required by the
|
| /Zephyr-latest/doc/project/ |
| D | issues.rst | 6 To maintain traceability and relation between proposals, changes, features, and
8 relevant GitHub issues and vice versa.
13 At any time it should be possible to establish the origin of a change and the
26 expertise and can be used by every one.
33 * Once the bisection is over and a culprit identified, verify manually the result.
|
| /Zephyr-latest/doc/develop/optimizations/ |
| D | footprint.rst | 11 should start the optimization process by reviewing all stack sizes and adjusting
44 the running application and provide means for debugging and error handling:
58 Depending on your application and platform needs, you can disable MPU/MMU
59 support to gain some memory and improve performance. Consider the consequences
61 checking and support.
|
1...<<11121314151617181920>>...155
