Home
last modified time | relevance | path

Searched +full:nrf21540 +full:- +full:gpio +full:- +full:if (Results 1 – 13 of 13) sorted by relevance

/Zephyr-latest/dts/bindings/net/wireless/
Dnordic,nrf21540-fem.yaml2 # SPDX-License-Identifier: Apache-2.0
6 This is a representation of the nRF21540 Radio Front-End module.
8 See the "nordic,nrf21540-fem-spi" binding to configure the SPI
11 the FEM and SPI configurations using the spi-if property.
13 Here is an example nRF21540 configuration with a SPI interface
17 compatible = "nordic,nrf-spim";
19 cs-gpios = <&gpio1 3 GPIO_ACTIVE_LOW>;
22 my_spi_if: nrf21540-spi@0 {
23 compatible = "nordic,nrf21540-fem-spi";
25 spi-max-frequency = <8000000>;
[all …]
Dnordic,nrf-radio.yaml2 # SPDX-License-Identifier: Apache-2.0
15 Front-End Module (FEM) support
16 ------------------------------
18 External front-end modules are range extenders used for boosting
19 the link robustness and link budget of wireless SoCs. If your
27 nrf_radio_fem: my-fem {
34 - generic-fem-two-ctrl-pins
35 - nordic,nrf21540-fem
41 ---------------------------
44 The 'dfe-supported' property will be set when it is available.
[all …]
/Zephyr-latest/dts/bindings/gpio/
Dnordic,nrf-gpio-forwarder.yaml2 # SPDX-License-Identifier: Apache-2.0
7 In nRF53 family of SoCs, GPIO pins must be explicitly forwarded by
8 the application core to the network core if the latter should drive them.
9 The purpose of this abstract device is to represent all GPIO pins that the
12 Once the control over selected GPIO pins is forwarded to it, the network
15 Here is an example of how a nrf-gpio-forwarder can be used with a nRF5340
16 combined with a nRF21540 Front-End module. Consider the following node
18 the details of the nRF21540 Front-End module's interface:
20 nrf_radio_fem: nrf21540 {
21 compatible = "nordic,nrf21540-fem";
[all …]
/Zephyr-latest/samples/net/sockets/echo_client/boards/
Dmimxrt1020_evk.overlay5 * SPDX-License-Identifier: Apache-2.0
9 * imxrt1020_evk -> HOST
10 * nRF21540-DK -> RCP (nrf/samples/openthread/coprocessor)
12 * nRF21540 (P6) P0.08 RXD -> IMXRT1020-EVK (J17) D1 (GPIO B1 08) (TXD)
13 * nRF21540 (P6) P0.07 CTS -> IMXRT1020-EVK (J19) D8 (GPIO B1 07) (RTS)
14 * nRF21540 (P6) P0.06 TXD -> IMXRT1020-EVK (J17) D0 (GPIO B1 09) (RXD)
15 * nRF21540 (P6) P0.05 RTS -> IMXRT1020-EVK (J17) D7 (GPIO B1 06) (CTS)
25 zephyr,hdlc-rcp-if = &hdlc_rcp_if;
26 zephyr,ot-uart = &lpuart2;
30 compatible = "uart,hdlc-rcp-if";
[all …]
/Zephyr-latest/samples/bluetooth/hci_uart/boards/
Dnrf5340_audio_dk_nrf5340_cpuapp_nrf21540_ek.overlay1 /* SPDX-License-Identifier: Apache-2.0 */
4 gpio_fwd: nrf-gpio-forwarder {
5 compatible = "nordic,nrf-gpio-forwarder";
8 nrf21540-gpio-if {
9 gpios = <&arduino_header 11 0>, /* tx-en-gpios */
10 <&arduino_header 9 0>, /* rx-en-gpios */
11 <&arduino_header 15 0>, /* pdn-gpios */
12 <&arduino_header 10 0>, /* ant-sel-gpios */
13 <&arduino_header 8 0>; /* mode-gpios */
16 nrf21540-spi-if {
[all …]
/Zephyr-latest/boards/nordic/nrf21540dk/doc/
Dindex.rst3 nRF21540 DK
8 The nRF21540 DK (PCA10112) shows possibility of the Nordic Semiconductor
9 nRF21540 Front End Module connected with nRF52840 ARM Cortex-M4F CPU.
15 * :abbr:`GPIO (General Purpose Input Output)`
16 * :abbr:`I2C (Inter-Integrated Circuit)`
24 * :abbr:`UART (Universal asynchronous receiver-transmitter)`
30 :alt: nRF21540 DK
32 nRF21540 DK (Credit: Nordic Semiconductor)
34 More information about the board can be found at the `nRF21540 website`_.
35 `nRF21540 Product Specification`_ contains the processor's and front end
[all …]
/Zephyr-latest/boards/nordic/nrf21540dk/
Dnrf21540dk_nrf52840.dts5 * SPDX-License-Identifier: Apache-2.0
8 /dts-v1/;
10 #include "nrf21540dk_nrf52840-pinctrl.dtsi"
11 #include <zephyr/dt-bindings/input/input-event-codes.h>
14 model = "Nordic nRF21540 DK NRF52840";
15 compatible = "nordic,nrf21540-dk-nrf52840";
19 zephyr,shell-uart = &uart0;
20 zephyr,uart-mcumgr = &uart0;
21 zephyr,bt-mon-uart = &uart0;
22 zephyr,bt-c2h-uart = &uart0;
[all …]
/Zephyr-latest/samples/net/sockets/echo_client/
DREADME.rst1 .. zephyr:code-sample:: sockets-echo-client
3 :relevant-api: bsd_sockets tls_credentials
10 The echo-client sample application for Zephyr implements a UDP/TCP client
20 - :ref:`networking_with_host`
26 usage scenario is to run echo-client application inside QEMU. This is
30 echo-client directory:
32 - :file:`prj.conf`
35 - :file:`overlay-ot.conf`
38 - :file:`overlay-802154.conf`
44 - :file:`overlay-qemu_802154.conf`
[all …]
/Zephyr-latest/boards/nordic/thingy53/
Dthingy53_nrf5340_cpunet.dts4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
9 #include "thingy53_nrf5340_cpunet-pinctrl.dtsi"
10 #include <zephyr/dt-bindings/input/input-event-codes.h>
14 compatible = "nordic,thingy53-nrf5340-cpunet";
18 zephyr,shell-uart = &uart0;
19 zephyr,uart-mcumgr = &uart0;
20 zephyr,bt-mon-uart = &uart0;
21 zephyr,bt-c2h-uart = &uart0;
22 zephyr,bt-hci-ipc = &ipc0;
[all …]
Dthingy53_nrf5340_common.dtsi4 * SPDX-License-Identifier: Apache-2.0
6 #include "thingy53_nrf5340_common-pinctrl.dtsi"
7 #include <zephyr/dt-bindings/input/input-event-codes.h>
8 #include <zephyr/dt-bindings/battery/battery.h>
12 zephyr,bt-hci-ipc = &ipc0;
13 zephyr,bt-hci = &bt_hci_ipc0;
14 nordic,802154-spinel-ipc = &ipc0;
19 compatible = "gpio-keys";
33 compatible = "gpio-leds";
49 compatible = "pwm-leds";
[all …]
/Zephyr-latest/doc/releases/
Drelease-notes-2.4.rst33 * CVE-2020-10060: UpdateHub Might Dereference An Uninitialized Pointer
34 * CVE-2020-10064: Improper Input Frame Validation in ieee802154 Processing
35 * CVE-2020-10066: Incorrect Error Handling in Bluetooth HCI core
36 * CVE-2020-10072: all threads can access all socket file descriptors
37 * CVE-2020-13598: FS: Buffer Overflow when enabling Long File Names in FAT_FS and calling fs_stat
38 * CVE-2020-13599: Security problem with settings and littlefs
39 * CVE-2020-13601: Under embargo until 2020/11/18
40 * CVE-2020-13602: Remote Denial of Service in LwM2M do_write_op_tlv
50 <https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aissue+is%3Aopen+label%3Abug>`_.
62 * The :c:func:`wdt_feed` function will now return ``-EAGAIN`` if
[all …]
Drelease-notes-2.6.rst13 * Added support for 64-bit ARCv3
14 * Split ARM32 and ARM64, ARM64 is now a top-level architecture
15 * Added initial support for Arm v8.1-m and Cortex-M55
22 https://github.com/zephyrproject-rtos/example-application
34 * CVE-2021-3581: Under embargo until 2021-09-04
41 <https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aissue+is%3Aopen+label%3Abug>`_.
46 * Driver APIs now return ``-ENOSYS`` if optional functions are not implemented.
47 If the feature is not supported by the hardware ``-ENOTSUP`` will be returned.
48 Formerly ``-ENOTSUP`` was returned for both failure modes, meaning this change
194 * Added support for null pointer dereferencing detection in Cortex-M.
[all …]
Drelease-notes-3.3.rst14 * Introduced :ref:`USB-C <usbc_api>` device stack with PD (power delivery)
17 CMSIS-DSP as the default backend.
30 * CVE-2023-0359: Under embargo until 2023-04-20
32 * CVE-2023-0779: Under embargo until 2023-04-22
66 removed in favor of new :dtcompatible:`zephyr,flash-disk` devicetree binding.
71 * Starting from this release ``zephyr-`` prefixed tags won't be created
82 image states). Use of a truncated hash or non-sha256 hash will still work
88 registration function at boot-up. If applications register this then
93 application code, these will now automatically be registered at boot-up (this
95 :kconfig:option:`CONFIG_MCUMGR_TRANSPORT_UDP_AUTOMATIC_INIT`). If
[all …]